)]}'
{
  "commit": "ff6f5157e034f81c2d6482259fc656cd0fe5a8ff",
  "tree": "829db06971b3900b274aa125a0883e57b911effe",
  "parents": [
    "fc13ba44da197a186f2f4d77c5b7d73d0f99f053",
    "71198b59df56a9a0115115091cc1aad2a4e3c74d"
  ],
  "author": {
    "name": "Jakub Kicinski",
    "email": "kuba@kernel.org",
    "time": "Thu Oct 08 10:49:26 2026 -0700"
  },
  "committer": {
    "name": "Jakub Kicinski",
    "email": "kuba@kernel.org",
    "time": "Thu Oct 08 10:49:26 2026 -0700"
  },
  "message": "Merge branch \u0027mlxsw-fix-port-range-register-leak\u0027\n\nPetr Machata says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nmlxsw: Fix port range register leak\n\nWhen the mlxsw driver parses a port range template rule, it acquires the\nactual port range registers. The parsing is only done to determine the\nelement usage, so the registers can be deallocated right away, but this is\nnever done, and the registers are leaked. Plug this leak and add a selftest\nthat would have caught it.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nLink: https://patch.msgid.link/cover.1791294384.git.petrm@nvidia.com\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n",
  "tree_diff": []
}