From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ v3 0/6] Add helper for "cleanup" variable attribute
Date: Tue, 12 May 2026 19:20:11 +0000 [thread overview]
Message-ID: <177861361154.3045511.1045324340041670862.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260511132131.1283892-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 Mon, 11 May 2026 15:18:03 +0200 you wrote:
> As discussed in:
> https://lore.kernel.org/linux-bluetooth/ed949f2550f79a4bef19bd482bf8b069ad5b7e0c.camel@hadess.net/
>
> Implement a cleanup helper.
>
> The MIN/MAX fix is here because it touches the same hunk in src/main.c
> as the other patches. Feel free to pick it up straight away while the
> rest is discussed.
>
> [...]
Here is the summary with links:
- [BlueZ,v3,1/6] all: Remove more unneeded MIN/MAX macro definition
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ca2b39b0c08e
- [BlueZ,v3,2/6] shared/util: Add helper for "cleanup" variable attribute
(no matching commit)
- [BlueZ,v3,3/6] doc: Recommend using _cleanup_ and friends
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9ba6c13df5fb
- [BlueZ,v3,4/6] main: Use _cleanup_() to simplify configuration parsing
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=140e3569295c
- [BlueZ,v3,5/6] client: Use _cleanup_fd_ to simplify urandom access
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e33f5027b898
- [BlueZ,v3,6/6] btattach: Use _cleanup_fd_ to simplify error paths
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=02aa9a8cfe6a
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-05-12 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 13:18 [BlueZ v3 0/6] Add helper for "cleanup" variable attribute Bastien Nocera
2026-05-11 13:18 ` [BlueZ v3 1/6] all: Remove more unneeded MIN/MAX macro definition Bastien Nocera
2026-05-11 17:27 ` Add helper for "cleanup" variable attribute bluez.test.bot
2026-05-11 13:18 ` [BlueZ v3 2/6] shared/util: " Bastien Nocera
2026-05-11 13:18 ` [BlueZ v3 3/6] doc: Recommend using _cleanup_ and friends Bastien Nocera
2026-05-11 13:18 ` [BlueZ v3 4/6] main: Use _cleanup_() to simplify configuration parsing Bastien Nocera
2026-05-11 13:35 ` [BlueZ,v3,4/6] " bluez.test.bot
2026-05-11 13:18 ` [BlueZ v3 5/6] client: Use _cleanup_fd_ to simplify urandom access Bastien Nocera
2026-05-11 13:18 ` [BlueZ v3 6/6] btattach: Use _cleanup_fd_ to simplify error paths Bastien Nocera
2026-05-12 19: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=177861361154.3045511.1045324340041670862.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