From: patchwork-bot+bluetooth@kernel.org
To: Archie Pusaka <apusaka@google.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
chromeos-bluetooth-upstreaming@chromium.org,
apusaka@chromium.org
Subject: Re: [PATCH Bluez 1/2] monitor: define manufacturer company IDs
Date: Tue, 14 Apr 2026 21:00:09 +0000 [thread overview]
Message-ID: <177620040979.1468596.8665372680347270723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260414111307.3725821-1-apusaka@google.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 14 Apr 2026 19:11:10 +0800 you wrote:
> From: Archie Pusaka <apusaka@chromium.org>
>
> Define company IDs to make it more readable.
> Also remove an unnecessary if that could cause uninitialized variable
> warning.
> ---
>
> [...]
Here is the summary with links:
- [Bluez,1/2] monitor: define manufacturer company IDs
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=babc5699226b
- [Bluez,2/2] monitor: Set msft_opcode on read_local_version_rsp
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=510623fb53b5
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:[~2026-04-14 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 11:11 [PATCH Bluez 1/2] monitor: define manufacturer company IDs Archie Pusaka
2026-04-14 11:11 ` [PATCH Bluez 2/2] monitor: Set msft_opcode on read_local_version_rsp Archie Pusaka
2026-04-14 12:24 ` [Bluez,1/2] monitor: define manufacturer company IDs bluez.test.bot
2026-04-14 21:00 ` 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=177620040979.1468596.8665372680347270723.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=apusaka@chromium.org \
--cc=apusaka@google.com \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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