From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ 0/2] Documentation fixups
Date: Mon, 26 Jan 2026 22:10:05 +0000 [thread overview]
Message-ID: <176946540585.196436.4757082840100826538.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260122170001.122052-1-hadess@hadess.net>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 22 Jan 2026 17:58:56 +0100 you wrote:
> Some documentation fixups after "Port text docs to RST and move man
> pages" got merged.
>
> Bastien Nocera (2):
> doc: Add "C" code-block markers for coding-style doc
> doc: Update .gitignore for new daemon man page locations
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] doc: Add "C" code-block markers for coding-style doc
(no matching commit)
- [BlueZ,2/2] doc: Update .gitignore for new daemon man page locations
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3f21f7817a40
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-01-26 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 16:58 [BlueZ 0/2] Documentation fixups Bastien Nocera
2026-01-22 16:58 ` [BlueZ 1/2] doc: Add "C" code-block markers for coding-style doc Bastien Nocera
2026-01-22 18:10 ` Luiz Augusto von Dentz
2026-01-22 18:23 ` Documentation fixups bluez.test.bot
2026-01-22 16:58 ` [BlueZ 2/2] doc: Update .gitignore for new daemon man page locations Bastien Nocera
2026-01-26 22: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=176946540585.196436.4757082840100826538.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.