All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org, luiz.von.dentz@intel.com,
	der.timosch@gmail.com
Subject: Re: [PATCH v2] Bluetooth: fix connection setup in l2cap_connect
Date: Mon, 10 Jun 2024 14:03:31 +0000	[thread overview]
Message-ID: <171802821189.16143.4037295666100940791.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ad69720e0ba720209cb04240fbc3c5ff059accbc.1717945321.git.pav@iki.fi>

Hello:

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

On Sun,  9 Jun 2024 18:06:20 +0300 you wrote:
> The amp_id argument of l2cap_connect() was removed in
> commit 84a4bb6548a2 ("Bluetooth: HCI: Remove HCI_AMP support")
> 
> It was always called with amp_id == 0, i.e. AMP_ID_BREDR == 0x00 (ie.
> non-AMP controller).  In the above commit, the code path for amp_id != 0
> was preserved, although it should have used the amp_id == 0 one.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: fix connection setup in l2cap_connect
    https://git.kernel.org/bluetooth/bluetooth-next/c/5fe0be8868aa

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-06-10 14:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 20:46 Bluetooth Kernel Bug: After connecting either HFP/HSP or A2DP is not available (Regression in 6.9.3, 6.8.12) Timo Schröder
2024-06-06 21:23 ` Luiz Augusto von Dentz
2024-06-07  6:10   ` Linux regression tracking (Thorsten Leemhuis)
2024-06-07 21:43     ` Timo Schröder
2024-06-07 22:00       ` Luiz Augusto von Dentz
2024-06-08 12:24         ` Timo Schröder
2024-06-07  3:55 ` Paul Menzel
2024-06-08 12:23   ` Timo Schröder
2024-06-08 21:59 ` [PATCH] Bluetooth: fix connection setup in l2cap_connect Pauli Virtanen
2024-06-08 22:03   ` kernel test robot
2024-06-08 22:31   ` bluez.test.bot
2024-06-09 12:49   ` [PATCH] " Timo Schröder
2024-06-09 15:01     ` Pauli Virtanen
2024-06-09 15:06 ` [PATCH v2] " Pauli Virtanen
2024-06-09 15:32   ` [v2] " bluez.test.bot
2024-06-09 16:29   ` [PATCH v2] " Timo Schröder
2024-06-09 17:41   ` Luiz Augusto von Dentz
2024-06-10 14:03   ` 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=171802821189.16143.4037295666100940791.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=der.timosch@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.von.dentz@intel.com \
    --cc=pav@iki.fi \
    /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.