From: Jakub Kicinski <kuba@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: davem@davemloft.net, linux-bluetooth@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2022-07-22
Date: Fri, 22 Jul 2022 16:55:10 -0700 [thread overview]
Message-ID: <20220722165510.191fad93@kernel.org> (raw)
In-Reply-To: <20220722205400.847019-1-luiz.dentz@gmail.com>
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
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...
next prev parent reply other threads:[~2022-07-22 23:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 20:54 pull request: bluetooth-next 2022-07-22 Luiz Augusto von Dentz
2022-07-22 23:55 ` Jakub Kicinski [this message]
2022-07-23 0:09 ` Luiz Augusto von Dentz
2022-07-23 0:19 ` Jakub Kicinski
2022-07-23 0:25 ` Luiz Augusto von Dentz
2022-07-23 0:50 ` Jakub Kicinski
2022-07-26 22:05 ` Luiz Augusto von Dentz
2022-07-26 22:31 ` Jakub Kicinski
2022-07-27 1:06 ` Luiz Augusto von Dentz
2022-07-27 2:47 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2022-07-23 0:22 Luiz Augusto von Dentz
2022-07-23 2:10 ` patchwork-bot+netdevbpf
2022-08-01 21:15 ` patchwork-bot+bluetooth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220722165510.191fad93@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).