[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABBYNZLj2z_81p=q0iSxEBgVW_L3dw8UKGwQKOEDj9fgDLYJ0g@mail.gmail.com>
Date: Fri, 22 Jul 2022 17:09:33 -0700
From: Luiz Augusto von Dentz <luiz.dentz@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: David Miller <davem@...emloft.net>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>
Subject: Re: pull request: bluetooth-next 2022-07-22
Hi Jakub,
On Fri, Jul 22, 2022 at 4:55 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Fri, 22 Jul 2022 13:54:00 -0700 Luiz Augusto von Dentz wrote:
> > The following changes since commit 6e0e846ee2ab01bc44254e6a0a6a6a0db1cba16d:
> >
> > Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2022-07-21 13:03:39 -0700)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git tags/for-net-next-2022-07-22
> >
> > for you to fetch changes up to 768677808478ee7ffabf9c9128f345b7ec62b5f3:
> >
> > Bluetooth: btusb: Detect if an ACL packet is in fact an ISO packet (2022-07-22 13:24:55 -0700)
> >
> > ----------------------------------------------------------------
> > bluetooth-next pull request for net-next:
> >
> > - Add support for IM Networks PID 0x3568
> > - Add support for BCM4349B1
> > - Add support for CYW55572
> > - Add support for MT7922 VID/PID 0489/e0e2
> > - Add support for Realtek RTL8852C
> > - Initial support for Isochronous Channels/ISO sockets
> > - Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING quirk
>
> I see two new sparse warnings (for a follow up):
>
> net/bluetooth/hci_event.c:3789:26: warning: cast to restricted __le16
> net/bluetooth/hci_event.c:3791:26: warning: cast to restricted __le16
Crap, let me fix them.
> Two bad Fixes tags:
>
> Commit: 68253f3cd715 ("Bluetooth: hci_sync: Fix resuming scan after suspend resume")
> Fixes tag: Fixes: 3b42055388c30 (Bluetooth: hci_sync: Fix attempting to suspend with
> Has these problem(s):
> - Subject has leading but no trailing parentheses
> Commit: 9111786492f1 ("Bluetooth: fix an error code in hci_register_dev()")
> Fixes tag: Fixes: d6bb2a91f95b ("Bluetooth: Unregister suspend with userchannel")
> Has these problem(s):
> - Target SHA1 does not exist
>
> And a whole bunch of patches committed by you but signed off by Marcel.
> Last time we tried to fix that it ended up making things worse.
> So I guess it is what it is :) Pulling...
Yep, that happens when I rebase on top of net-next so I would have to
redo all the Signed-off-by lines if the patches were originally
applied by Marcel, at least I don't know of any option to keep the
original committer while rebasing?
--
Luiz Augusto von Dentz
Powered by blists - more mailing lists