From: patchwork-bot+bluetooth@kernel.org
To: Christian Eggers <ceggers@arri.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/9] doc: mesh-api: minor copy&paste fix
Date: Fri, 27 Jun 2025 17:00:07 +0000 [thread overview]
Message-ID: <175104360724.1996502.15314023353118607724.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250627075928.19788-1-ceggers@arri.de>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 27 Jun 2025 09:59:20 +0200 you wrote:
> ---
> doc/mesh-api.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [BlueZ,1/9] doc: mesh-api: minor copy&paste fix
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6983c985e08a
- [BlueZ,2/9] mesh: keyring: constify
(no matching commit)
- [BlueZ,3/9] mesh: mesh-config: constify
(no matching commit)
- [BlueZ,4/9] mesh: util: constify
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b913bd1b92a4
- [BlueZ,5/9] mesh: mesh_net_transport_send: simplify
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=725a72ea654c
- [BlueZ,6/9] mesh: node_add_pending_local: use concrete type
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2874aeb4d056
- [BlueZ,7/9] mesh: remove unused function typedef
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2a40b2f8e07a
- [BlueZ,8/9] net: packet_received: avoid unnecessary copying
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2251e6d79620
- [BlueZ,9/9] tools: parser: fix printf format errors
(no matching commit)
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-06-27 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 7:59 [PATCH BlueZ 1/9] doc: mesh-api: minor copy&paste fix Christian Eggers
2025-06-27 7:59 ` [PATCH BlueZ 2/9] mesh: keyring: constify Christian Eggers
2025-06-27 7:59 ` [PATCH BlueZ 3/9] mesh: mesh-config: constify Christian Eggers
2025-06-27 7:59 ` [PATCH BlueZ 4/9] mesh: util: constify Christian Eggers
2025-06-27 7:59 ` [PATCH BlueZ 5/9] mesh: mesh_net_transport_send: simplify Christian Eggers
2025-06-27 7:59 ` [PATCH BlueZ 6/9] mesh: node_add_pending_local: use concrete type Christian Eggers
2025-06-27 7:59 ` [PATCH BlueZ 7/9] mesh: remove unused function typedef Christian Eggers
2025-06-27 7:59 ` [PATCH BlueZ 8/9] net: packet_received: avoid unnecessary copying Christian Eggers
2025-06-27 7:59 ` [PATCH BlueZ 9/9] tools: parser: fix printf format errors Christian Eggers
2025-06-27 9:32 ` [BlueZ,1/9] doc: mesh-api: minor copy&paste fix bluez.test.bot
2025-06-27 17:00 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-27 7:57 [PATCH BlueZ 1/9] " Christian Eggers
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=175104360724.1996502.15314023353118607724.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=ceggers@arri.de \
--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.