public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
	chethan.tumkur.narayan@intel.com
Subject: Re: [PATCH v1 1/2] bluetooth: Remove codec id field in vendor codec definition
Date: Thu, 01 Dec 2022 20:00:18 +0000	[thread overview]
Message-ID: <166992481807.20187.14128711456819746834.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221104071810.22720-1-kiran.k@intel.com>

Hello:

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

On Fri,  4 Nov 2022 12:48:09 +0530 you wrote:
> From: Chethan T N <chethan.tumkur.narayan@intel.com>
> 
> As per the specfication vendor codec id is defined.
> BLUETOOTH CORE SPECIFICATION Version 5.3 | Vol 4, Part E page 2127
> 
> Signed-off-by: Chethan T N <chethan.tumkur.narayan@intel.com>
> Signed-off-by: Kiran K <kiran.k@intel.com>
> 
> [...]

Here is the summary with links:
  - [v1,1/2] bluetooth: Remove codec id field in vendor codec definition
    https://git.kernel.org/bluetooth/bluetooth-next/c/f0d0a36e32ab
  - [v1,2/2] bluetooth: Fix support for Read Local Supported Codecs V2
    https://git.kernel.org/bluetooth/bluetooth-next/c/fb77b0482a8a

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



      parent reply	other threads:[~2022-12-01 20:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  7:18 [PATCH v1 1/2] bluetooth: Remove codec id field in vendor codec definition Kiran K
2022-11-04  7:18 ` [PATCH v1 2/2] bluetooth: Fix support for Read Local Supported Codecs V2 Kiran K
2022-11-04  8:03 ` [v1,1/2] bluetooth: Remove codec id field in vendor codec definition bluez.test.bot
2022-11-16 20:57 ` [PATCH v1 1/2] " Luiz Augusto von Dentz
2022-11-18  3:48 ` [v1,1/2] " bluez.test.bot
2022-11-18  4:34 ` bluez.test.bot
2022-11-18  5:30 ` bluez.test.bot
2022-11-18  6:34 ` bluez.test.bot
2022-11-18  7:33 ` bluez.test.bot
2022-11-18  8:36 ` bluez.test.bot
2022-11-18  9:31 ` bluez.test.bot
2022-11-19  3:56 ` bluez.test.bot
2022-11-19  5:02 ` bluez.test.bot
2022-12-01 20:00 ` patchwork-bot+bluetooth [this message]

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=166992481807.20187.14128711456819746834.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ravishankar.srivatsa@intel.com \
    /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