[Kernel-packages] [Bug 2033551] Re: mlxbf_bootctl: replace SAUCE patches with upstream

2023-10-18 Thread Bartlomiej Zolnierkiewicz
Mark the verification as already done using the new tag.

** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2033551

Title:
  mlxbf_bootctl: replace SAUCE patches with upstream

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_bootctl BlueField platform driver in the Jammy repo
  consists of some SAUCE patches.  These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality.  One patch for the
  mlxbf_bootctl driver is not yet upstreamed, so that patch will
  remain as SAUCE patch for now.

  [Test Case]
  * Boot BF2/BF3 platform, verify no new errors
  * Program MFG fields via "bfcfg" tool:
 1) With current image, use 'bfcfg -d' to display current values
 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info'
 3) With new image, use 'bfcfg' to push new or same MFG fields
 4) Verify that the MFG fields are programmed properly via 'bfcfg -d'
 5) Repeat process to replace proper MFG fields
  * Display BlueField boot log
 1) cd /sys/bus/platform/devices/MLNXBF04:00
 2) cat rsh_log
 3) Should see boot log entries relevant to last boot

  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been 
  well-tested and the functionality is the same.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2033551] Re: mlxbf_bootctl: replace SAUCE patches with upstream

2023-10-06 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 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-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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!


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2033551

Title:
  mlxbf_bootctl: replace SAUCE patches with upstream

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_bootctl BlueField platform driver in the Jammy repo
  consists of some SAUCE patches.  These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality.  One patch for the
  mlxbf_bootctl driver is not yet upstreamed, so that patch will
  remain as SAUCE patch for now.

  [Test Case]
  * Boot BF2/BF3 platform, verify no new errors
  * Program MFG fields via "bfcfg" tool:
 1) With current image, use 'bfcfg -d' to display current values
 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info'
 3) With new image, use 'bfcfg' to push new or same MFG fields
 4) Verify that the MFG fields are programmed properly via 'bfcfg -d'
 5) Repeat process to replace proper MFG fields
  * Display BlueField boot log
 1) cd /sys/bus/platform/devices/MLNXBF04:00
 2) cat rsh_log
 3) Should see boot log entries relevant to last boot

  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been 
  well-tested and the functionality is the same.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2033551] Re: mlxbf_bootctl: replace SAUCE patches with upstream

2023-10-06 Thread Feysel Mohammed
** Tags removed: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2033551

Title:
  mlxbf_bootctl: replace SAUCE patches with upstream

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_bootctl BlueField platform driver in the Jammy repo
  consists of some SAUCE patches.  These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality.  One patch for the
  mlxbf_bootctl driver is not yet upstreamed, so that patch will
  remain as SAUCE patch for now.

  [Test Case]
  * Boot BF2/BF3 platform, verify no new errors
  * Program MFG fields via "bfcfg" tool:
 1) With current image, use 'bfcfg -d' to display current values
 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info'
 3) With new image, use 'bfcfg' to push new or same MFG fields
 4) Verify that the MFG fields are programmed properly via 'bfcfg -d'
 5) Repeat process to replace proper MFG fields
  * Display BlueField boot log
 1) cd /sys/bus/platform/devices/MLNXBF04:00
 2) cat rsh_log
 3) Should see boot log entries relevant to last boot

  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been 
  well-tested and the functionality is the same.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2033551] Re: mlxbf_bootctl: replace SAUCE patches with upstream

2023-10-03 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 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-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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!


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2033551

Title:
  mlxbf_bootctl: replace SAUCE patches with upstream

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_bootctl BlueField platform driver in the Jammy repo
  consists of some SAUCE patches.  These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality.  One patch for the
  mlxbf_bootctl driver is not yet upstreamed, so that patch will
  remain as SAUCE patch for now.

  [Test Case]
  * Boot BF2/BF3 platform, verify no new errors
  * Program MFG fields via "bfcfg" tool:
 1) With current image, use 'bfcfg -d' to display current values
 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info'
 3) With new image, use 'bfcfg' to push new or same MFG fields
 4) Verify that the MFG fields are programmed properly via 'bfcfg -d'
 5) Repeat process to replace proper MFG fields
  * Display BlueField boot log
 1) cd /sys/bus/platform/devices/MLNXBF04:00
 2) cat rsh_log
 3) Should see boot log entries relevant to last boot

  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been 
  well-tested and the functionality is the same.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2033551] Re: mlxbf_bootctl: replace SAUCE patches with upstream

2023-09-25 Thread Bartlomiej Zolnierkiewicz
This bug is awaiting verification that the linux-
bluefield/5.15.0-1025.27 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!


** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2033551

Title:
  mlxbf_bootctl: replace SAUCE patches with upstream

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_bootctl BlueField platform driver in the Jammy repo
  consists of some SAUCE patches.  These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality.  One patch for the
  mlxbf_bootctl driver is not yet upstreamed, so that patch will
  remain as SAUCE patch for now.

  [Test Case]
  * Boot BF2/BF3 platform, verify no new errors
  * Program MFG fields via "bfcfg" tool:
 1) With current image, use 'bfcfg -d' to display current values
 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info'
 3) With new image, use 'bfcfg' to push new or same MFG fields
 4) Verify that the MFG fields are programmed properly via 'bfcfg -d'
 5) Repeat process to replace proper MFG fields
  * Display BlueField boot log
 1) cd /sys/bus/platform/devices/MLNXBF04:00
 2) cat rsh_log
 3) Should see boot log entries relevant to last boot

  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been 
  well-tested and the functionality is the same.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2033551] Re: mlxbf_bootctl: replace SAUCE patches with upstream

2023-09-20 Thread Bartlomiej Zolnierkiewicz
** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2033551

Title:
  mlxbf_bootctl: replace SAUCE patches with upstream

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_bootctl BlueField platform driver in the Jammy repo
  consists of some SAUCE patches.  These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality.  One patch for the
  mlxbf_bootctl driver is not yet upstreamed, so that patch will
  remain as SAUCE patch for now.

  [Test Case]
  * Boot BF2/BF3 platform, verify no new errors
  * Program MFG fields via "bfcfg" tool:
 1) With current image, use 'bfcfg -d' to display current values
 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info'
 3) With new image, use 'bfcfg' to push new or same MFG fields
 4) Verify that the MFG fields are programmed properly via 'bfcfg -d'
 5) Repeat process to replace proper MFG fields
  * Display BlueField boot log
 1) cd /sys/bus/platform/devices/MLNXBF04:00
 2) cat rsh_log
 3) Should see boot log entries relevant to last boot

  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been 
  well-tested and the functionality is the same.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2033551] Re: mlxbf_bootctl: replace SAUCE patches with upstream

2023-09-14 Thread Bartlomiej Zolnierkiewicz
** Also affects: linux-bluefield (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux-bluefield (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2033551

Title:
  mlxbf_bootctl: replace SAUCE patches with upstream

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  New

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_bootctl BlueField platform driver in the Jammy repo
  consists of some SAUCE patches.  These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality.  One patch for the
  mlxbf_bootctl driver is not yet upstreamed, so that patch will
  remain as SAUCE patch for now.

  [Test Case]
  * Boot BF2/BF3 platform, verify no new errors
  * Program MFG fields via "bfcfg" tool:
 1) With current image, use 'bfcfg -d' to display current values
 2) Reboot, stopping at UEFI menu, trigger 'Reset MFG Info'
 3) With new image, use 'bfcfg' to push new or same MFG fields
 4) Verify that the MFG fields are programmed properly via 'bfcfg -d'
 5) Repeat process to replace proper MFG fields
  * Display BlueField boot log
 1) cd /sys/bus/platform/devices/MLNXBF04:00
 2) cat rsh_log
 3) Should see boot log entries relevant to last boot

  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been 
  well-tested and the functionality is the same.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2033551/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp