From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/3] Remove glib dep from non-glib shared library
Date: Thu, 16 Apr 2026 15:20:06 +0000 [thread overview]
Message-ID: <177635280653.3275927.901198944484854482.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260416141021.3970323-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, 16 Apr 2026 16:08:39 +0200 you wrote:
> Changes since v1:
> - remove queue_peek_head_entry() patch, we already had similar API
>
> Bastien Nocera (3):
> shared: Remove glib dependency from src/shared/ad.c
> shared/queue: Fix warning when compiling ad.c
> shared: Remove unneeded glib includes
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/3] shared: Remove glib dependency from src/shared/ad.c
(no matching commit)
- [BlueZ,v2,2/3] shared/queue: Fix warning when compiling ad.c
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6a6aaeba6aed
- [BlueZ,v2,3/3] shared: Remove unneeded glib includes
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=07a0b87e6b34
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 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 14:08 [PATCH BlueZ v2 0/3] Remove glib dep from non-glib shared library Bastien Nocera
2026-04-16 14:08 ` [PATCH BlueZ v2 1/3] shared: Remove glib dependency from src/shared/ad.c Bastien Nocera
2026-04-16 14:08 ` [PATCH BlueZ v2 2/3] shared/queue: Fix warning when compiling ad.c Bastien Nocera
2026-04-16 14:08 ` [PATCH BlueZ v2 3/3] shared: Remove unneeded glib includes Bastien Nocera
2026-04-16 15:20 ` 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=177635280653.3275927.901198944484854482.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox