linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: bluetooth-next 2025-05-21
Date: Thu, 22 May 2025 09:53:15 -0700	[thread overview]
Message-ID: <20250522095315.158eee1a@kernel.org> (raw)
In-Reply-To: <20250521144756.3033239-1-luiz.dentz@gmail.com>

On Wed, 21 May 2025 10:47:55 -0400 Luiz Augusto von Dentz wrote:
> The following changes since commit e6b3527c3b0a676c710e91798c2709cc0538d312:
> 
>   Merge branch 'net-airoha-add-per-flow-stats-support-to-hw-flowtable-offloading' (2025-05-20 20:00:55 -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-2025-05-21
> 
> for you to fetch changes up to 623029dcc53837d409deb70b65eb7c7b83ab9b9a:
> 
>   Bluetooth: MGMT: iterate over mesh commands in mgmt_mesh_foreach() (2025-05-21 10:31:01 -0400)

Another bad fixes tag :( Time to automate this on your side?

Commit: ee1d8d65dffd ("Bluetooth: L2CAP: Fix not checking l2cap_chan security level")
	Fixes tag: Fixes: 50c1241e6a8a ("Bluetooth: l2cap: Check encryption key size on incoming connection")
	Has these problem(s):
		- Target SHA1 does not exist
-- 
pw-bot: cr

  reply	other threads:[~2025-05-22 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21 14:47 bluetooth-next 2025-05-21 Luiz Augusto von Dentz
2025-05-22 16:53 ` Jakub Kicinski [this message]
2025-05-22 17:02   ` Luiz Augusto von Dentz
2025-05-22 17:05     ` Jakub Kicinski

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=20250522095315.158eee1a@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).