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: [GIT PULL] bluetooth 2025-05-07
Date: Wed, 7 May 2025 17:55:00 -0700 [thread overview]
Message-ID: <20250507175500.2d725b00@kernel.org> (raw)
In-Reply-To: <20250507170320.277453-1-luiz.dentz@gmail.com>
On Wed, 7 May 2025 13:03:20 -0400 Luiz Augusto von Dentz wrote:
> bluetooth pull request for net:
>
> - MGMT: Fix MGMT_OP_ADD_DEVICE invalid device flags
> - hci_event: Fix not using key encryption size when its known
Looks like we have a tatty Fixes tag in here:
Commit: 9840f8ecc910 ("Bluetooth: hci_event: Fix not using key encryption size when its known") Fixes tag: Fixes: 50c1241e6a8a ("Bluetooth: l2cap: Check encryption key size on incoming connection")
Has these problem(s):
- Target SHA1 does not exist
next prev parent reply other threads:[~2025-05-08 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 17:03 [GIT PULL] bluetooth 2025-05-07 Luiz Augusto von Dentz
2025-05-08 0:55 ` Jakub Kicinski [this message]
2025-05-08 14:06 ` Luiz Augusto von Dentz
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=20250507175500.2d725b00@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).