From: patchwork-bot+bluetooth@kernel.org
To: Calvin Owens <calvin@wbinvd.org>
Cc: linux-kernel@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, sean.wang@mediatek.com,
amitkumar.karwar@nxp.com, neeraj.sanjaykale@nxp.com,
linux-bluetooth@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, johan.hedberg@intel.com
Subject: Re: [PATCH] Bluetooth: remove duplicate h4_recv_buf() in header
Date: Fri, 29 Aug 2025 16:40:07 +0000 [thread overview]
Message-ID: <175648560766.2276001.11700293691359487684.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <be8edf7f8ba8dea6c61272b02fb20a4ac7e1c5a5.1756179634.git.calvin@wbinvd.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 25 Aug 2025 21:11:08 -0700 you wrote:
> The "h4_recv.h" header contains a duplicate h4_recv_buf() that is nearly
> but not quite identical to the h4_recv_buf() in hci_h4.c.
>
> This duplicated header was added in commit 07eb96a5a7b0 ("Bluetooth:
> bpa10x: Use separate h4_recv_buf helper"). I wasn't able to find any
> explanation for duplicating the code in the discussion:
>
> [...]
Here is the summary with links:
- Bluetooth: remove duplicate h4_recv_buf() in header
https://git.kernel.org/bluetooth/bluetooth-next/c/0e272fc7e17d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-30 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 4:11 [PATCH] Bluetooth: remove duplicate h4_recv_buf() in header Calvin Owens
2025-08-26 5:40 ` Paul Menzel
2025-08-26 5:44 ` Paul Menzel
2025-08-29 16: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=175648560766.2276001.11700293691359487684.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=calvin@wbinvd.org \
--cc=johan.hedberg@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
--cc=neeraj.sanjaykale@nxp.com \
--cc=sean.wang@mediatek.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 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).