mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-bluefield (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Committed
|
Medium
|
Unassigned |
Bug Description
SRU Justification:
[Impact]
The Jammy repo contains the following SAUCE patch:
UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read
This patch is now in mainline Linux kernel, so the SAUCE patch
can be reverted and replaced with the upstream commit SHA.
[Fix]
The fix requires two parts, the first of which is addressed by
this bug. A second bug will be created to add the upstream
commit to the repo. The fix to this bug is a revert of the SAUCE patch
8d2dbbd437a1 UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read
[Test Case]
Boot platform and bring up "oob_net0" interface properly
Test that network traffic works properly
[Regression Potential]
Low, as this logic is well tested.
[Other]
Will add a note to this bug with the second bug's number,
after the second bug is created. The second bug is for
adding the upstream commit to the Jammy repo.
Changed in linux-bluefield (Ubuntu Jammy): | |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux-bluefield (Ubuntu): | |
status: | New → Invalid |
Changed in linux-bluefield (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-jammy removed: verification-needed-jammy |
This bug is within the Jammy repo of the BlueField project (22.04).
I sent in the patch with a subject line containing this prefix: F:linux- bluefield] " Is that relevant for 22.04 patches,
"[SRU][
or should the "F" be replaced with something to signify Jammy?