From: Kiran K <kiran.k@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: ravishankar.srivatsa@intel.com, chethan.tumkur.narayan@intel.com,
luiz.von.dentz@intel.com, Kiran K <kiran.k@intel.com>
Subject: [PATCH v1 6/7] Bluetooth: Remove unused member in struct hci_vnd_codec_v2
Date: Fri, 8 Oct 2021 19:28:52 +0530 [thread overview]
Message-ID: <20211008135853.8604-6-kiran.k@intel.com> (raw)
In-Reply-To: <20211008135853.8604-1-kiran.k@intel.com>
Remove unused "u8 id" member in struct hci_vnd_codec_v2. Vendor codec
is identifiable by Company Id and Vendor Id fields.
Change-Id: I466f0ecac850115d15dfe72a943fbf3f31baf18d
---
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 451d491f7f68..7ea1bfce204f 100644
--- a/include/net/bluetooth/hci.h
+++ b/include/net/bluetooth/hci.h
@@ -1393,7 +1393,6 @@ struct hci_std_codecs_v2 {
} __packed;
struct hci_vnd_codec_v2 {
- __u8 id;
__le16 cid;
__le16 vid;
__u8 transport;
--
2.17.1
next prev parent reply other threads:[~2021-10-08 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 13:58 [PATCH v1 1/7] Bluetooth: Refactor code to read supported codecs in getsockopt Kiran K
2021-10-08 13:58 ` [PATCH v1 2/7] Bluetooth: Support reading of codecs supported over l2cap socket Kiran K
2021-10-08 13:58 ` [PATCH v1 3/7] Bluetooth: btintel: cache offload use case data Kiran K
2021-10-08 13:58 ` [PATCH v1 4/7] Bluetooth: Pass transport type in get_data_path_id Kiran K
2021-10-08 13:58 ` [PATCH v1 5/7] Bluetooth: btintel: Add support to fetch data path id for a2dp offload Kiran K
2021-10-08 13:58 ` Kiran K [this message]
2021-10-08 13:58 ` [PATCH v1 7/7] Bluetooth: Read Output codec capabilities Kiran K
2021-10-08 14:00 ` [PATCH v1 1/7] Bluetooth: Refactor code to read supported codecs in getsockopt K, Kiran
2021-10-08 15:07 ` [v1,1/7] " bluez.test.bot
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=20211008135853.8604-6-kiran.k@intel.com \
--to=kiran.k@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).