From: Kiran K <kiran.k@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: ravishankar.srivatsa@intel.com,
Chethan T N <chethan.tumkur.narayan@intel.com>,
Kiran K <kiran.k@intel.com>
Subject: [PATCH v1 1/2] bluetooth: Remove codec id field in vendor codec definition
Date: Fri, 4 Nov 2022 12:48:09 +0530 [thread overview]
Message-ID: <20221104071810.22720-1-kiran.k@intel.com> (raw)
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>
---
include/net/bluetooth/hci.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/net/bluetooth/hci.h b/include/net/bluetooth/hci.h
index e004ba04a9ae..581539cbb856 100644
--- a/include/net/bluetooth/hci.h
+++ b/include/net/bluetooth/hci.h
@@ -1424,7 +1424,6 @@ struct hci_std_codecs_v2 {
} __packed;
struct hci_vnd_codec_v2 {
- __u8 id;
__le16 cid;
__le16 vid;
__u8 transport;
--
2.17.1
next reply other threads:[~2022-11-04 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 7:18 Kiran K [this message]
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 ` [PATCH v1 1/2] " 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=20221104071810.22720-1-kiran.k@intel.com \
--to=kiran.k@intel.com \
--cc=chethan.tumkur.narayan@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