)]}'
{
  "commit": "03d0beff9856a569d0da91ea0ccdc28045c2b2d0",
  "tree": "0008a1e92f56326039672b6b5f9c87d18ccaf444",
  "parents": [
    "0ba3aa254ae9d48ec0b2ecfa5fda5c391862a36b"
  ],
  "author": {
    "name": "Lukasz Czapnik",
    "email": "lukasz.czapnik@intel.com",
    "time": "Thu May 21 13:50:00 2026 +0200"
  },
  "committer": {
    "name": "Tony Nguyen",
    "email": "anthony.l.nguyen@intel.com",
    "time": "Fri May 29 11:12:42 2026 -0700"
  },
  "message": "ice: use ACL for ntuple rules that conflict with FDir\n\nFlow Director can keep only one input set per flow type. After ACL support\nwas added for ethtool ntuple rules, the driver still only selected ACL for\nrules with partial masks.\n\nThat leaves a gap for rules with full masks that still require a different\ninput set than the one already programmed for Flow Director. Such rules go\nthrough the FDir path, build a different extraction sequence and then fail\nbecause the existing FDir profile cannot be reused.\n\nDetect this case before programming the rule. Build the candidate IP flow\nsegment, compare it with the active non-tunneled FDir profile and, when the\ninput sets differ, offload the rule through ACL if ACL is available.\n\nRefactor the IP flow segment setup into a helper so the same logic can be\nused both by the extraction-sequence configuration path and by the conflict\ncheck.\n\nSigned-off-by: Lukasz Czapnik \u003clukasz.czapnik@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "955dca313a8d9a43ae7c2a3f0576318d3b59ae5d",
      "old_mode": 33188,
      "old_path": "drivers/net/ethernet/intel/ice/ice_ethtool_ntuple.c",
      "new_id": "aabcbf2247316cd8a55239f4a0d54defe3f2fb76",
      "new_mode": 33188,
      "new_path": "drivers/net/ethernet/intel/ice/ice_ethtool_ntuple.c"
    }
  ]
}