From: patchwork-bot+bluetooth@kernel.org
To: Calvin Owens <calvin@wbinvd.org>
Cc: luiz.dentz@gmail.com, pmenzel@molgen.mpg.de,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
luiz.von.dentz@intel.com, oe-kbuild-all@lists.linux.dev,
marcel@holtmann.org, sean.wang@mediatek.com,
linux-mediatek@lists.infradead.org, naresh.kamboju@linaro.org
Subject: Re: [PATCH v2] Bluetooth: Fix build after header cleanup
Date: Tue, 02 Sep 2025 16:20:07 +0000 [thread overview]
Message-ID: <175683000705.361492.473758022048124463.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <aLcQsE3x9o4BzXxp@mozart.vkv.me>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 2 Sep 2025 08:43:44 -0700 you wrote:
> Some Kconfig dependencies are needed after my recent cleanup, since
> the core code has its own option.
>
> Since btmtksdio does not actually call h4_recv_buf(), move the
> definitions it uses outside the BT_HCIUART_H4 gate in hci_uart.h to
> avoid adding a dependency for btmtksdio.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: Fix build after header cleanup
https://git.kernel.org/bluetooth/bluetooth-next/c/16ebf6c26de5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-02 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202508300413.OnIedvRh-lkp@intel.com>
2025-08-30 0:50 ` [PATCH] Bluetooth: btmtksdio: Fix build after header cleanup Calvin Owens
2025-08-30 5:11 ` Paul Menzel
2025-08-30 19:32 ` Calvin Owens
2025-09-02 15:29 ` Luiz Augusto von Dentz
2025-09-02 15:43 ` [PATCH v2] Bluetooth: " Calvin Owens
2025-09-02 16:20 ` patchwork-bot+bluetooth [this message]
2025-09-03 14:04 ` Calvin Owens
2025-09-03 14:06 ` [PATCH v3] " Calvin Owens
2025-09-03 15:29 ` Paul Menzel
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=175683000705.361492.473758022048124463.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=calvin@wbinvd.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=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=naresh.kamboju@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pmenzel@molgen.mpg.de \
--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).