)]}'
{
  "commit": "062bb97410835055036490c96cf77898f90d34ea",
  "tree": "ec15bd3a4cd30eb3e850fefab025bd6d4ab48e47",
  "parents": [
    "f13663ffb1457ce12a9b14df0c1b3229ea18af5f"
  ],
  "author": {
    "name": "Mark Brown",
    "email": "broonie@kernel.org",
    "time": "Mon Jun 17 23:54:46 2024 +0100"
  },
  "committer": {
    "name": "Mark Brown",
    "email": "broonie@kernel.org",
    "time": "Fri Feb 27 00:48:03 2026 +0000"
  },
  "message": "regmap: Print error messages for ranges where the window and range overlap\n\nWe support accessed to paged register ranges, we describe these by having\nthe regmap assign a range of virtual register numbers to the underlying\nregisters and specify the window in the physical register map through which\nthey can be accessed, along with the register used to move the window.\nThings get very confused if the window and virtual range overlap since it\nis unclear how to access registers in the window, do we need to page to\nthem or not?\n\nUnfortunately the code neither detects cases where the range and window\noverlap nor blows up obviously when encountering them so we\u0027ve got quite a\nfew broken drivers. Try to prevent any more creeping in by logging errors\nif we see such regmaps.\n\nReported-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nSigned-off-by: Mark Brown \u003cbroonie@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "607c1246d994a17a7f4c73e3492f61be17d19b16",
      "old_mode": 33188,
      "old_path": "drivers/base/regmap/regmap.c",
      "new_id": "9ca7061ac67299804dfa9b326f216c076199ce20",
      "new_mode": 33188,
      "new_path": "drivers/base/regmap/regmap.c"
    }
  ]
}