APPLIED/Cmnt[J]: [SRU] [J/OEM-5.14] [PATCH 0/4] Add Bluetooth support for Qualcomm WCN6856

[Andrea Righi]

On Fri, Dec 24, 2021 at 10:39:33AM +0800, Kai-Heng Feng wrote:
> BugLink: https://bugs.launchpad.net/bugs/1955689
> 
> [Impact]
> WCN6856 Bluetooth doesn't work.
> 
> [Fix]
> Backport firmware blobs and driver support to make it work by loading
> correct firmwares.
> 
> [Test]
> Bluetooth scanning and pairing work, and continue to do so after several
> suspend/resume cycles.
> 
> [Where problems could occur]
> The upstream version of btusb_generate_qca_nvm_name() adds several
> missing le*_to_cpu() macros, so if this device was ever used on a Big
> Endian system, this is a behavioral change.

I think the order of the patches for jammy is incorrect. This is what I
see from your email:

  [J] [PATCH] Bluetooth: btusb: Add the new support IDs for WCN6855
  [J/OEM-5.14] [PATCH 2/4] Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller
  [J/OEM-5.14] [PATCH 3/4] Bluetooth: btusb: re-definition for board_id in struct qca_version

But it looks like I need to apply the patch in this order:

  [J][PATCH 1/3] Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller
  [J][PATCH 2/3] Bluetooth: btusb: re-definition for board_id in struct qca_version
  [J][PATCH 3/3] Bluetooth: btusb: Add the new support IDs for WCN6855

Moreover, I've updated the cherry-picked lines (linux-next -> linux),
because all these commits are now upstream.

Assuming all the above is correct: applied to jammy/linux.

-Andrea