mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"

[David Thompson]

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.

[David Thompson (dthompso-98)]

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:
"[SRU][F:linux-bluefield]" Is that relevant for 22.04 patches,
or should the "F" be replaced with something to signify Jammy?

[David Thompson (dthompso-98)]

Sorry as this has become confusing. This bug does still apply to Jammy linux-bluefield,
and the fix is contained in a patch series that I sent in yesterday:
v3-0000-cover-letter.patch
v3-0001-UBUNTU-SAUCE-Revert-UBUNTU-SAUCE-mlxbf_gige-clear.patch
v3-0002-mlxbf_gige-clear-MDIO-gateway-lock-after-read.patch

Please let me know if indeed this bug is being closed and I need to create
another LP bug for the v3 patch series.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-bluefield/5.15.0-1009.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-bluefield/5.15.0-1010.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!