Thread (2 messages) 2 messages, 2 authors, 2025-01-31

Re: linux-next: duplicate patches in the bluetooth tree

From: Paolo Abeni <pabeni@redhat.com>
Date: 2025-01-31 07:37:57
Also in: linux-next, lkml

Hi,

On 1/31/25 3:16 AM, Stephen Rothwell wrote:
The following commits are also in the net tree as different commits
(but the same patches):

  07b6216dfc34 ("Bluetooth: Add ABI doc for sysfs reset")
  52f17be9931e ("Bluetooth: btnxpuart: Fix glitches seen in dual A2DP streaming")
  56cec66d6163 ("Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection")
  9e2714de7384 ("Bluetooth: Fix possible infinite recursion of btusb_reset")
  ec5570088c6a ("Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface()")
I pulled from:

git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git
tags/for-net-2025-01-29

AFAICS net hashes match the above tag. @Luiz: did you by chance rebased
your tree before tagging it and sending the PR? Just to understand the
root cause of the above difference.

Thanks,

Paolo




Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help