)]}'
{
  "commit": "5b02e8cfbd95b502553f8cb5fcb6f1ccdbecfbad",
  "tree": "51e3b67b79bdaae9c83d1c5cd55b953d0ec7ca75",
  "parents": [
    "013574567a60c427c36dbc2a5ff25fec69f9c4b6"
  ],
  "author": {
    "name": "Jonathan Cameron",
    "email": "Jonathan.Cameron@huawei.com",
    "time": "Mon Aug 07 20:24:16 2023 +0100"
  },
  "committer": {
    "name": "Jonathan Cameron",
    "email": "Jonathan.Cameron@huawei.com",
    "time": "Mon Aug 07 20:24:16 2023 +0100"
  },
  "message": "iio: light: opt4001: Fix a wrong array iteration limit\n\nIn practice it\u0027s unlikely anyone would try to set the integration time\nto 0 which isn\u0027t in the available list and if they did then they would\nget index 12 which whilst reserved on the device fits in the field.\nHowever a compiler might get half way through this reasoning and that\nmight be the cause of\n\n\u003e \u003e\u003e drivers/iio/light/opt4001.c:215:9: error: call to \u0027__compiletime_assert_355\u0027 declared with \u0027error\u0027 attribute: FIELD_PREP: value too large for the field\n\u003e      215 |         reg |\u003d FIELD_PREP(OPT4001_CTRL_CONV_TIME_MASK, chip-\u003eint_time);\n\nEven if this isn\u0027t the cause, it looks like a bug to me.\n\nFixes: 9a9608418292 (\"iio: light: Add support for TI OPT4001 light sensor\")\nReported-by: kernel test robot \u003clkp@intel.com\u003e\nCloses: https://lore.kernel.org/oe-kbuild-all/202308061902.0gVz6bSe-lkp@intel.com/\nSigned-off-by: Jonathan Cameron \u003cJonathan.Cameron@huawei.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "502946bf9f946f9ef97ff3f60d81b89f55ebadf6",
      "old_mode": 33188,
      "old_path": "drivers/iio/light/opt4001.c",
      "new_id": "83f97870675803d44783bbfcc49e716ed60c7fde",
      "new_mode": 33188,
      "new_path": "drivers/iio/light/opt4001.c"
    }
  ]
}