From: patchwork-bot+bluetooth@kernel.org
To: Marek Vasut <marex@denx.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] tools: Make hciattach_* firmware path build-time configurable
Date: Tue, 01 Nov 2022 21:10:16 +0000 [thread overview]
Message-ID: <166733701667.25446.5293406780135758558.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221101115333.18223-1-marex@denx.de>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 1 Nov 2022 12:53:33 +0100 you wrote:
> Make hciattach_qualcomm.c and hciattach_tialt.c behave the same way
> as hciattach_bcm43xx.c does, where FIRMWARE_DIR can be overridden
> at build time by using -DFIRMWARE_DIR= CFLAGS.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> tools/hciattach.h | 4 ++++
> tools/hciattach_bcm43xx.c | 4 ----
> tools/hciattach_qualcomm.c | 3 ++-
> tools/hciattach_tialt.c | 3 ++-
> 4 files changed, 8 insertions(+), 6 deletions(-)
Here is the summary with links:
- [BlueZ] tools: Make hciattach_* firmware path build-time configurable
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d9253248363b
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:[~2022-11-01 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 11:53 [PATCH BlueZ] tools: Make hciattach_* firmware path build-time configurable Marek Vasut
2022-11-01 13:37 ` [BlueZ] " bluez.test.bot
2022-11-01 15:19 ` Marek Vasut
2022-11-01 19:24 ` Luiz Augusto von Dentz
2022-11-01 20:27 ` Marek Vasut
2022-11-01 21:10 ` 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=166733701667.25446.5293406780135758558.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marex@denx.de \
/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