public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Arun Raghavan <arun@arunraghavan.net>
Cc: arkadiusz.bokowy@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] media: Fix G.722 @ 16 kHz codec ID value reported by transport
Date: Thu, 29 Jan 2026 16:30:05 +0000	[thread overview]
Message-ID: <176970420584.2563498.10397591263771732571.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260129154755.410853-1-arun@arunraghavan.net>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu, 29 Jan 2026 07:47:52 -0800 you wrote:
> The G.722 @ 16 kHz codec ID is 0x01, not 0x02. The 0x02 value comes from
> the ASHA ReadOnlyProperties GATT characteristic which is a bitmask with
> bits corresponding to codec IDs - setting bit 1 gives bitmask value 0x02.
> 
> Reviewed-by: Arun Raghavan <arun@arunraghavan.net>
> ---
>  profiles/audio/media.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Here is the summary with links:
  - media: Fix G.722 @ 16 kHz codec ID value reported by transport
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ebb33150ba76

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2026-01-29 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 10:38 [PATCH] media: Fix G.722 @ 16 kHz codec ID value reported by transport Arkadiusz Bokowy
2026-01-28 11:34 ` bluez.test.bot
2026-01-29 15:47 ` [PATCH] " Arun Raghavan
2026-01-29 15:53   ` Arun Raghavan
2026-01-29 16:30   ` patchwork-bot+bluetooth [this message]
2026-01-29 16:43   ` bluez.test.bot
2026-01-29 16:30 ` [PATCH] " 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=176970420584.2563498.10397591263771732571.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=arkadiusz.bokowy@gmail.com \
    --cc=arun@arunraghavan.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