public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 0e74c4: shared/util: Add MIN/MAX implementations
Date: Tue, 31 Mar 2026 14:59:59 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1075447/000000-c446bf@github.com> (raw)

  Branch: refs/heads/1075447
  Home:   https://github.com/bluez/bluez
  Commit: 0e74c4e43ddb701b8db16504b8b5c0273baac1c4
      https://github.com/bluez/bluez/commit/0e74c4e43ddb701b8db16504b8b5c0273baac1c4
  Author: Bastien Nocera <hadess@hadess.net>
  Date:   2026-03-31 (Tue, 31 Mar 2026)

  Changed paths:
    M src/sdpd-request.c
    M src/shared/util.h

  Log Message:
  -----------
  shared/util: Add MIN/MAX implementations

And remove it from src/sdpd-request.c to avoid a redefinition warning
at compile-time.


  Commit: c446bfe3cb10b8d2ce52661a715a3dfdaf576ebf
      https://github.com/bluez/bluez/commit/c446bfe3cb10b8d2ce52661a715a3dfdaf576ebf
  Author: Bastien Nocera <hadess@hadess.net>
  Date:   2026-03-31 (Tue, 31 Mar 2026)

  Changed paths:
    M emulator/btdev.c

  Log Message:
  -----------
  emulator: Remove compile-time header only glib dep

btvirt relied on a glib header macro to use MIN/MAX, but didn't link
against it, meaning that it was dependent on other programs in the
project using glib to compile correctly.

Remove the include and use our own implementation instead.


Compare: https://github.com/bluez/bluez/compare/0e74c4e43ddb%5E...c446bfe3cb10

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-03-31 22:00 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/1075447/000000-c446bf@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