)]}'
{
  "commit": "6c1f5146b214f281a04ceeff7608845f1818c4f2",
  "tree": "94d76c6d98fec1cbc4213cd1c341bece70d8b7c3",
  "parents": [
    "3879cffd9d07aa0377c4b8835c4f64b4fb24ac78",
    "faba5860fcf9a0ae49d2e484397bce44293367ff"
  ],
  "author": {
    "name": "Marc Kleine-Budde",
    "email": "mkl@pengutronix.de",
    "time": "Thu Jan 15 09:52:34 2026 +0100"
  },
  "committer": {
    "name": "Marc Kleine-Budde",
    "email": "mkl@pengutronix.de",
    "time": "Thu Jan 15 09:52:34 2026 +0100"
  },
  "message": "Merge patch series \"can: raw: better approach to instantly reject unsupported CAN frames\"\n\nOliver Hartkopp \u003csocketcan@hartkopp.net\u003e says:\n\nThis series reverts commit 1a620a723853 (\"can: raw: instantly reject\nunsupported CAN frames\").\n\nand its follow-up fixes for the introduced dependency issues.\n\ncommit 1a620a723853 (\"can: raw: instantly reject unsupported CAN frames\")\ncommit cb2dc6d2869a (\"can: Kconfig: select CAN driver infrastructure by default\")\ncommit 6abd4577bccc (\"can: fix build dependency\")\ncommit 5a5aff6338c0 (\"can: fix build dependency\")\n\nThe reverted patch was accessing CAN device internal data structures\nfrom the network layer because it needs to know about the CAN protocol\ncapabilities of the CAN devices.\n\nThis data access caused build problems between the CAN network and the\nCAN driver layer which introduced unwanted Kconfig dependencies and fixes.\n\nThe patches 2 \u0026 3 implement a better approach which makes use of the\nCAN specific ml_priv data which is accessible from both sides.\n\nWith this change the CAN network layer can check the required features\nand the decoupling of the driver layer and network layer is restored.\n\nLink: https://patch.msgid.link/20260109144135.8495-1-socketcan@hartkopp.net\n[mkl: give series a more descriptive name]\n[mkl: properly format reverted patch commitish]\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n",
  "tree_diff": []
}