From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] doc: Add missing btmon-cs doc to btmon.rst
Date: Thu, 16 Apr 2026 13:50:06 +0000 [thread overview]
Message-ID: <177634740604.2827737.7640411424955587978.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260416100323.3848182-1-hadess@hadess.net>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 16 Apr 2026 12:03:17 +0200 you wrote:
> ---
> Makefile.am | 2 ++
> doc/btmon.rst | 2 ++
> 2 files changed, 4 insertions(+)
Here is the summary with links:
- [BlueZ,v2] doc: Add missing btmon-cs doc to btmon.rst
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=590bed15fbaf
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-16 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 10:03 [PATCH BlueZ v2] doc: Add missing btmon-cs doc to btmon.rst Bastien Nocera
2026-04-16 12:10 ` [BlueZ,v2] " bluez.test.bot
2026-04-16 13:50 ` 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=177634740604.2827737.7640411424955587978.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/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.