From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v2 1/2] shared/util: Add MIN/MAX implementations
Date: Tue, 31 Mar 2026 23:36:36 +0200 [thread overview]
Message-ID: <20260331213731.3895736-2-hadess@hadess.net> (raw)
In-Reply-To: <20260331213731.3895736-1-hadess@hadess.net>
And remove it from src/sdpd-request.c to avoid a redefinition warning
at compile-time.
---
src/sdpd-request.c | 2 --
src/shared/util.h | 6 ++++++
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/src/sdpd-request.c b/src/sdpd-request.c
index 1fc07e97bfe0..7c632c2aaf62 100644
--- a/src/sdpd-request.c
+++ b/src/sdpd-request.c
@@ -40,8 +40,6 @@ typedef struct {
#define SDP_CONT_STATE_SIZE (sizeof(uint8_t) + sizeof(sdp_cont_state_t))
-#define MIN(x, y) ((x) < (y)) ? (x): (y)
-
typedef struct sdp_cont_info sdp_cont_info_t;
struct sdp_cont_info {
diff --git a/src/shared/util.h b/src/shared/util.h
index c480351d6e9f..67629dddfaa9 100644
--- a/src/shared/util.h
+++ b/src/shared/util.h
@@ -22,6 +22,12 @@
#define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]))
#define BIT(n) (1 << (n))
+#undef MIN
+#define MIN(a, b) ((a) < (b) ? (a) : (b))
+
+#undef MAX
+#define MAX(a, b) ((a) > (b) ? (a) : (b))
+
#if __BYTE_ORDER == __LITTLE_ENDIAN
#define le16_to_cpu(val) (val)
#define le32_to_cpu(val) (val)
--
2.53.0
next prev parent reply other threads:[~2026-03-31 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 21:36 [PATCH BlueZ v2 0/2] shared/util: Add MIN/MAX implementations Bastien Nocera
2026-03-31 21:36 ` Bastien Nocera [this message]
2026-03-31 22:47 ` bluez.test.bot
2026-03-31 21:36 ` [PATCH BlueZ v2 2/2] emulator: Remove compile-time header only glib dep Bastien Nocera
2026-04-01 14:30 ` [PATCH BlueZ v2 0/2] shared/util: Add MIN/MAX implementations patchwork-bot+bluetooth
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=20260331213731.3895736-2-hadess@hadess.net \
--to=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