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] b36d2b: unit: Add unit test for new MIN/MAX macros
Date: Wed, 01 Apr 2026 14:23:56 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1076045/000000-1e294a@github.com> (raw)

  Branch: refs/heads/1076045
  Home:   https://github.com/bluez/bluez
  Commit: b36d2b00c8d0c0dd1471921b2aa0704860dfd3af
      https://github.com/bluez/bluez/commit/b36d2b00c8d0c0dd1471921b2aa0704860dfd3af
  Author: Bastien Nocera <hadess@hadess.net>
  Date:   2026-04-01 (Wed, 01 Apr 2026)

  Changed paths:
    M Makefile.am
    A unit/test-util.c

  Log Message:
  -----------
  unit: Add unit test for new MIN/MAX macros


  Commit: 1e294ad65ec8001956c96375ea6e816e26b1aaa0
      https://github.com/bluez/bluez/commit/1e294ad65ec8001956c96375ea6e816e26b1aaa0
  Author: Bastien Nocera <hadess@hadess.net>
  Date:   2026-04-01 (Wed, 01 Apr 2026)

  Changed paths:
    M client/mgmt.c
    M mesh/prov-initiator.c
    M src/device.c
    M src/gatt-database.c
    M src/shared/gatt-client.c
    M src/shared/gatt-helpers.c
    M src/shared/ringbuf.c
    M src/shared/uhid.c
    M src/shared/vcp.h
    M tools/advtest.c
    M tools/btgatt-server.c
    M tools/hcitool.c
    M tools/parser/rfcomm.h

  Log Message:
  -----------
  all: Remove redundant MIN/MAX macro definitions


Compare: https://github.com/bluez/bluez/compare/b36d2b00c8d0%5E...1e294ad65ec8

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

                 reply	other threads:[~2026-04-01 21:23 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/1076045/000000-1e294a@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