From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] eff7db: all: Remove more unneeded MIN/MAX macro definition
Date: Wed, 06 May 2026 08:55:44 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1090532/000000-dc4d19@github.com> (raw)
Branch: refs/heads/1090532
Home: https://github.com/bluez/bluez
Commit: eff7db7ed10341dd510b0a045d31a49761f8dc4e
https://github.com/bluez/bluez/commit/eff7db7ed10341dd510b0a045d31a49761f8dc4e
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-05-06 (Wed, 06 May 2026)
Changed paths:
M lib/bluetooth/hci.c
M src/main.c
M src/shared/gatt-server.c
Log Message:
-----------
all: Remove more unneeded MIN/MAX macro definition
Commit: c3200ddcfe6913d6959dc0baf2a66a42a58bf371
https://github.com/bluez/bluez/commit/c3200ddcfe6913d6959dc0baf2a66a42a58bf371
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-05-06 (Wed, 06 May 2026)
Changed paths:
M src/shared/util.h
Log Message:
-----------
shared/util: Add helper for "cleanup" variable attribute
Use the widespread "cleanup" variable attribute:
https://gcc.gnu.org/onlinedocs/gcc/Common-Attributes.html#index-cleanup
It is implemented by both GCC and clang on platforms where bluez is
used, and can help reduce memory leaks, while improving readability.
See also:
https://systemd.io/CODING_STYLE/#memory-allocation
https://docs.gtk.org/glib/auto-cleanup.html
Commit: 706acaec9481a82aef2833b51a4c001cb96beea2
https://github.com/bluez/bluez/commit/706acaec9481a82aef2833b51a4c001cb96beea2
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-05-06 (Wed, 06 May 2026)
Changed paths:
M doc/maintainer-guidelines.rst
Log Message:
-----------
doc: Recommend using _cleanup_ and friends
Commit: 5b442f494b6c9eba048ff06500d29d9b93f78821
https://github.com/bluez/bluez/commit/5b442f494b6c9eba048ff06500d29d9b93f78821
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-05-06 (Wed, 06 May 2026)
Changed paths:
M src/main.c
Log Message:
-----------
main: Use _cleanup_() to simplify configuration parsing
Makes dealing with the error path easier.
Commit: dc4d19132e80ae285d9d7fbe776dad85b43f7121
https://github.com/bluez/bluez/commit/dc4d19132e80ae285d9d7fbe776dad85b43f7121
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-05-06 (Wed, 06 May 2026)
Changed paths:
M src/main.c
Log Message:
-----------
main: Use _cleanup_() to simplify GError-handling
Use _cleanup_() to simplify GError-handling in the error paths.
Compare: https://github.com/bluez/bluez/compare/eff7db7ed103%5E...dc4d19132e80
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-05-06 15:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1090532/000000-dc4d19@github.com \
--to=noreply@github.com \
--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