From: Paolo Abeni <pabeni@redhat.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
davem@davemloft.net, kuba@kernel.org
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: bluetooth 2024-10-30
Date: Thu, 31 Oct 2024 11:52:33 +0100 [thread overview]
Message-ID: <1c19403a-e192-44bf-9158-9ac132174c40@redhat.com> (raw)
In-Reply-To: <20241030192205.38298-1-luiz.dentz@gmail.com>
On 10/30/24 20:22, Luiz Augusto von Dentz wrote:
> The following changes since commit c05c62850a8f035a267151dd86ea3daf887e28b8:
>
> Merge tag 'wireless-2024-10-29' of https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless (2024-10-29 18:57:12 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2024-10-30
>
> for you to fetch changes up to 1e67d8641813f1876a42eeb4f532487b8a7fb0a8:
>
> Bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs (2024-10-30 14:49:09 -0400)
>
> ----------------------------------------------------------------
> bluetooth pull request for net:
>
> - hci: fix null-ptr-deref in hci_read_supported_codecs
>
> ----------------------------------------------------------------
> Sungwoo Kim (1):
> Bluetooth: hci: fix null-ptr-deref in hci_read_supported_codecs
FTR, there is a small buglet with the tag area in this commit (empty
line between fixes and SoB tag). Given we are still digesting last week
pw, I think is better to avoid rebase and repost, but please double
check such things in the future.
Thanks,
Paolo
next prev parent reply other threads:[~2024-10-31 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 19:22 pull request: bluetooth 2024-10-30 Luiz Augusto von Dentz
2024-10-31 10:52 ` Paolo Abeni [this message]
2024-11-01 1:21 ` patchwork-bot+netdevbpf
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=1c19403a-e192-44bf-9158-9ac132174c40@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--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).