All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Maheta@ci.codeaurora.org, Abhay <abhay.maheshbhai.maheta@intel.com>
Cc: linux-bluetooth@vger.kernel.org, mabhay125@gmail.com
Subject: Re: [PATCH BlueZ v3 0/6] To add support for Metadata, CID, VID
Date: Wed, 04 Jan 2023 00:30:17 +0000	[thread overview]
Message-ID: <167279221703.4957.7483450913741816466.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221229155257.341327-1-abhay.maheshbhai.maheta@intel.com>

Hello:

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

On Thu, 29 Dec 2022 21:22:53 +0530 you wrote:
> This series of patches adds support for Metadata, Company ID and
> Vendor Codec ID during Endpoint Registration for LE Audio.
> 
> Abhay Maheta (6):
>   shared/bap: Fix handling for Company ID and Vendor Codec ID
>   shared/bap: Add support to set stream metadata
>   profiles: Add Support for Metadata, CID and VID
>   media-api: Add CompanyID, VendorCodecID, Metadata
>   client/player: Add support for Company ID, Vendor ID
>   client/player: Add support for Metadata in BAP Profile
> 
> [...]

Here is the summary with links:
  - [BlueZ,v3,1/6] shared/bap: Fix handling for Company ID and Vendor Codec ID
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=441eeb2a1448
  - [BlueZ,v3,2/6] shared/bap: Add support to set stream metadata
    (no matching commit)
  - [BlueZ,v3,3/6] profiles: Add Support for Metadata, CID and VID
    (no matching commit)
  - [BlueZ,v3,4/6] media-api: Add CompanyID, VendorCodecID, Metadata
    (no matching commit)
  - [BlueZ,v3,5/6] client/player: Add support for Company ID, Vendor ID
    (no matching commit)
  - [BlueZ,v3,6/6] client/player: Add support for Metadata in BAP Profile
    (no matching commit)

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



      parent reply	other threads:[~2023-01-04  0:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-29 15:52 [PATCH BlueZ v3 0/6] To add support for Metadata, CID, VID Abhay Maheta
2022-12-29 15:52 ` [PATCH BlueZ v3 1/6] shared/bap: Fix handling for Company ID and Vendor Codec ID Abhay Maheta
2022-12-29 17:31   ` To add support for Metadata, CID, VID bluez.test.bot
2022-12-29 15:52 ` [PATCH BlueZ v3 2/6] shared/bap: Add support to set stream metadata Abhay Maheta
2023-01-04  0:24   ` Luiz Augusto von Dentz
2023-01-04 16:39     ` Maheta, Abhay
2022-12-29 15:52 ` [PATCH BlueZ v3 3/6] profiles: Add Support for Metadata, CID and VID Abhay Maheta
2022-12-29 15:53 ` [PATCH BlueZ v3 4/6] media-api: Add CompanyID, VendorCodecID, Metadata Abhay Maheta
2023-01-04  0:26   ` Luiz Augusto von Dentz
2022-12-29 15:53 ` [PATCH BlueZ v3 5/6] client/player: Add support for Company ID, Vendor ID Abhay Maheta
2023-01-04  0:41   ` Luiz Augusto von Dentz
2022-12-29 15:53 ` [PATCH BlueZ v3 6/6] client/player: Add support for Metadata in BAP Profile Abhay Maheta
2023-01-04  0:32   ` Luiz Augusto von Dentz
2023-01-04  0:30 ` 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=167279221703.4957.7483450913741816466.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=Maheta@ci.codeaurora.org \
    --cc=abhay.maheshbhai.maheta@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mabhay125@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.