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 2026-02-23
Date: Tue, 24 Feb 2026 16:29:09 -0800 [thread overview]
Message-ID: <20260224162909.047a1431@kernel.org> (raw)
In-Reply-To: <20260223211634.3800315-1-luiz.dentz@gmail.com>
On Mon, 23 Feb 2026 16:16:34 -0500 Luiz Augusto von Dentz wrote:
> bluetooth pull request for net:
>
> - purge error queues in socket destructors
> - hci_sync: Fix CIS host feature condition
> - L2CAP: Fix invalid response to L2CAP_ECRED_RECONF_REQ
> - L2CAP: Fix result of L2CAP_ECRED_CONN_RSP when MTU is too short
> - L2CAP: Fix response to L2CAP_ECRED_CONN_REQ
> - L2CAP: Fix not checking output MTU is acceptable on L2CAP_ECRED_CONN_REQ
> - L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ
> - hci_qca: Cleanup on all setup failures
Pulled (by Paolo), thanks!
next prev parent reply other threads:[~2026-02-25 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 21:16 [GIT PULL] bluetooth 2026-02-23 Luiz Augusto von Dentz
2026-02-25 0:29 ` Jakub Kicinski [this message]
2026-03-16 19:42 ` 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=20260224162909.047a1431@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