linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b0db5e: shared/hfp: Add extended response code enabling co...
Date: Tue, 04 Nov 2025 06:48:58 -0800	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/32d740-654c4f@github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: b0db5e1c330ade4cfa188105468aa6fd60293ab3
      https://github.com/bluez/bluez/commit/b0db5e1c330ade4cfa188105468aa6fd60293ab3
  Author: Frédéric Danis <frederic.danis@collabora.com>
  Date:   2025-11-04 (Tue, 04 Nov 2025)

  Changed paths:
    M src/shared/hfp.c
    M unit/test-hfp.c

  Log Message:
  -----------
  shared/hfp: Add extended response code enabling command


  Commit: f3904a8f1c2cae24bb19099143b2ea8e7511a7dd
      https://github.com/bluez/bluez/commit/f3904a8f1c2cae24bb19099143b2ea8e7511a7dd
  Author: Frédéric Danis <frederic.danis@collabora.com>
  Date:   2025-11-04 (Tue, 04 Nov 2025)

  Changed paths:
    M src/shared/hfp.c
    M unit/test-hfp.c

  Log Message:
  -----------
  shared/hfp: Add NREC disable command


  Commit: 654c4f5755e7ea4dafd34ec3b5498d3a961d1825
      https://github.com/bluez/bluez/commit/654c4f5755e7ea4dafd34ec3b5498d3a961d1825
  Author: Frédéric Danis <frederic.danis@collabora.com>
  Date:   2025-11-04 (Tue, 04 Nov 2025)

  Changed paths:
    M unit/test-hfp.c

  Log Message:
  -----------
  unit/test-hfp: Add ECNR off test

This add the following test:
- /HFP/HF/ENO/BV-01-C
  Verify that the HF can disable the EC/NR function of the AG.


Compare: https://github.com/bluez/bluez/compare/32d740d87970...654c4f5755e7

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

                 reply	other threads:[~2025-11-04 14:48 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/master/32d740-654c4f@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;
as well as URLs for NNTP newsgroup(s).