)]}'
{
  "commit": "31cf22099bc3243ba2779d55fba0282bbcf29ddf",
  "tree": "8eeb7e2664ad661476f4609e663f7e51df715d90",
  "parents": [
    "a10e08a9a3cb85a2e797b8e0683da9049f8792f8"
  ],
  "author": {
    "name": "Jonas Karlman",
    "email": "jonas@kwiboo.se",
    "time": "Fri May 10 19:35:51 2024 +0000"
  },
  "committer": {
    "name": "Tom Rini",
    "email": "trini@konsulko.com",
    "time": "Fri May 17 12:52:15 2024 -0600"
  },
  "message": "pinctrl: Fix pinctrl_gpio_get_pinctrl_and_offset()\n\nLinux kernel Documentation/devicetree/bindings/gpio/gpio.txt define the\nformat of the gpio-ranges prop as:\n\n  The format is: \u003c[pin controller phandle], [GPIO controller offset],\n                  [pin controller offset], [number of pins]\u003e;\n\n  Example:\n\n      gpio-ranges \u003d \u003c\u0026foo 0 20 10\u003e, \u003c\u0026bar 10 50 20\u003e;\n\n  This means:\n  - pins 20..29 on pin controller \"foo\" is mapped to GPIO line 0..9 and\n  - pins 50..69 on pin controller \"bar\" is mapped to GPIO line 10..29\n\nFor this example, a call to pinctrl_gpio_get_pinctrl_and_offset() using\noffset 10 incorrectly return pin controller \"foo\" instead of \"bar\".\n\nFix this by using an exclusive range check.\n\nFixes: d0bb00adccb8 (\"pinctrl: fix pinctrl_gpio_get_pinctrl_and_offset for gpio-ranges array\")\nSigned-off-by: Jonas Karlman \u003cjonas@kwiboo.se\u003e\nReviewed-by: Quanyang Wang \u003cquanyang.wang@windriver.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d9bda7494e23942e7d68c6f9ce50c1eb25d4d3f6",
      "old_mode": 33188,
      "old_path": "drivers/pinctrl/pinctrl-uclass.c",
      "new_id": "d9c76898a9692d40b7cd4eecf7cb2edf9e93a209",
      "new_mode": 33188,
      "new_path": "drivers/pinctrl/pinctrl-uclass.c"
    }
  ]
}