From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/5] profiles: Add Support for Metadata, CID and VID
Date: Wed, 01 Feb 2023 01:10:17 +0000 [thread overview]
Message-ID: <167521381735.32644.5977585726413771767.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230123235649.3231488-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 23 Jan 2023 15:56:45 -0800 you wrote:
> From: "Maheta, Abhay" <abhay.maheshbhai.maheta@intel.com>
>
> This adds support for Metadata, Company ID and Vendor Codec ID
> ---
> profiles/audio/bap.c | 7 ++-
> profiles/audio/media.c | 106 +++++++++++++++++++++++++++++++++----
> profiles/audio/transport.c | 4 +-
> 3 files changed, 105 insertions(+), 12 deletions(-)
Here is the summary with links:
- [BlueZ,1/5] profiles: Add Support for Metadata, CID and VID
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=17bcd2a37629
- [BlueZ,2/5] client/player: Add support for Company ID, Vendor ID
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=33d99e12c37f
- [BlueZ,3/5] shared/util: Check arguments on util_memcpy
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=be5c49385e4d
- [BlueZ,4/5] media-api: Make Vendor a uint32_t
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d611a40ffc7b
- [BlueZ,5/5] media: Rework support of Vendor to use uint32_t as type
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-01 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 23:56 [PATCH BlueZ 1/5] profiles: Add Support for Metadata, CID and VID Luiz Augusto von Dentz
2023-01-23 23:56 ` [PATCH BlueZ 2/5] client/player: Add support for Company ID, Vendor ID Luiz Augusto von Dentz
2023-01-23 23:56 ` [PATCH BlueZ 3/5] shared/util: Check arguments on util_memcpy Luiz Augusto von Dentz
2023-01-23 23:56 ` [PATCH BlueZ 4/5] media-api: Make Vendor a uint32_t Luiz Augusto von Dentz
2023-01-23 23:56 ` [PATCH BlueZ 5/5] media: Rework support of Vendor to use uint32_t as type Luiz Augusto von Dentz
2023-01-24 2:54 ` [BlueZ,1/5] profiles: Add Support for Metadata, CID and VID bluez.test.bot
2023-02-01 1:10 ` 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=167521381735.32644.5977585726413771767.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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.