All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Vinicius Peixoto <nukelet64@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	johan.hedberg@gmail.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Add new quirk for broken read key length on ATS2851
Date: Mon, 04 Mar 2024 21:40:27 +0000	[thread overview]
Message-ID: <170958842734.5292.12544056625468291768.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227014328.1052386-1-nukelet64@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon, 26 Feb 2024 22:43:26 -0300 you wrote:
> The ATS2851 controller erroneously reports support for the "Read
> Encryption Key Length" HCI command. This makes it unable to connect
> to any devices, since this command is issued by the kernel during the
> connection process in response to an "Encryption Change" HCI event.
> 
> Add a new quirk (HCI_QUIRK_BROKEN_ENC_KEY_SIZE) to hint that the command
> is unsupported, preventing it from interrupting the connection process.
> 
> [...]

Here is the summary with links:
  - Bluetooth: Add new quirk for broken read key length on ATS2851
    https://git.kernel.org/bluetooth/bluetooth-next/c/88f741deaa76

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-03-04 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27  1:43 [PATCH] Bluetooth: Add new quirk for broken read key length on ATS2851 Vinicius Peixoto
2024-02-27  2:38 ` bluez.test.bot
2024-03-04 21:40 ` patchwork-bot+bluetooth [this message]

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=170958842734.5292.12544056625468291768.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=nukelet64@gmail.com \
    --cc=pabeni@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.