From: kbuild test robot <lkp@intel.com>
To: Miao-chen Chou <mcchou@chromium.org>
Cc: kbuild-all@lists.01.org,
Bluetooth Kernel Mailing List <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v1 2/2] Bluetooth: btusb: Read the supported features of Microsoft vendor extension
Date: Tue, 24 Mar 2020 01:30:28 +0800 [thread overview]
Message-ID: <202003240100.nVNDVhCu%lkp@intel.com> (raw)
In-Reply-To: <20200323002820.v1.2.I4e01733fa5b818028dc9188ca91438fc54aa5028@changeid>
Hi Miao-chen,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bluetooth-next/master]
[also build test WARNING on next-20200323]
[cannot apply to v5.6-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Miao-chen-Chou/btusb-Introduce-the-use-of-vendor-extension-s/20200323-165723
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-187-gbff9b106-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> net/bluetooth/hci_event.c:1793:32: sparse: sparse: cast to restricted __le16
>> net/bluetooth/hci_event.c:1810:47: sparse: sparse: cast to restricted __le64
arch/x86/include/asm/bitops.h:77:37: sparse: sparse: cast truncates bits from constant value (ffffff7f becomes 7f)
arch/x86/include/asm/bitops.h:77:37: sparse: sparse: cast truncates bits from constant value (ffffff7f becomes 7f)
arch/x86/include/asm/bitops.h:77:37: sparse: sparse: cast truncates bits from constant value (ffffff7f becomes 7f)
arch/x86/include/asm/bitops.h:77:37: sparse: sparse: cast truncates bits from constant value (ffffff7f becomes 7f)
arch/x86/include/asm/bitops.h:77:37: sparse: sparse: cast truncates bits from constant value (ffffff7f becomes 7f)
vim +1793 net/bluetooth/hci_event.c
1788
1789 static void hci_cc_msft_vnd_ext(struct hci_dev *hdev, struct sk_buff *skb)
1790 {
1791 struct msft_cmd_cmp_info *info = (void *)skb->data;
1792 const u8 status = info->status;
> 1793 const u16 sub_opcode = __le16_to_cpu(info->sub_opcode);
1794
1795 skb_pull(skb, sizeof(*info));
1796
1797 if (status) {
1798 BT_ERR("Microsoft vendor extension sub command 0x%2.2x failed",
1799 sub_opcode);
1800 return;
1801 }
1802
1803 BT_DBG("%s status 0x%2.2x sub opcode 0x%2.2x", hdev->name, status,
1804 sub_opcode);
1805
1806 switch (sub_opcode) {
1807 case MSFT_OP_READ_SUPPORTED_FEATURES: {
1808 struct msft_rp_read_supported_features *rp = (void *)skb->data;
1809
> 1810 hdev->msft_vnd_ext_features = __le64_to_cpu(rp->features);
1811 hdev->msft_vnd_ext_evt_prefix_len = rp->msft_evt_prefix_len;
1812 hdev->msft_vnd_ext_evt_prefix =
1813 kmalloc(hdev->msft_vnd_ext_evt_prefix_len, GFP_ATOMIC);
1814 if (!hdev->msft_vnd_ext_evt_prefix)
1815 return;
1816
1817 memcpy(hdev->msft_vnd_ext_evt_prefix, rp->msft_evt_prefix,
1818 hdev->msft_vnd_ext_evt_prefix_len);
1819 BT_DBG("%s Microsoft vendor extension features 0x%016llx",
1820 hdev->name, hdev->msft_vnd_ext_features);
1821 break;
1822 }
1823 default:
1824 BT_ERR("%s unknown sub opcode 0x%2.2x", hdev->name,
1825 sub_opcode);
1826 break;
1827 }
1828 }
1829
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2020-03-23 17:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 7:28 [PATCH v1 0/2] btusb: Introduce the use of vendor extension(s) Miao-chen Chou
2020-03-23 7:28 ` [PATCH v1 1/2] Bluetooth: btusb: Indicate Microsoft vendor extension for Intel 9460/9560 and 9160/9260 Miao-chen Chou
2020-03-23 17:56 ` Marcel Holtmann
2020-03-23 18:45 ` Joe Perches
2020-03-23 18:48 ` Marcel Holtmann
2020-03-23 20:09 ` Joe Perches
2020-03-24 15:10 ` Alain Michaud
2020-03-24 15:17 ` Joe Perches
2020-03-24 15:24 ` Alain Michaud
2020-03-24 16:45 ` Joe Perches
2020-03-24 18:35 ` Marcel Holtmann
2020-03-24 19:32 ` Alain Michaud
2020-03-25 5:18 ` Miao-chen Chou
2020-03-25 8:02 ` Marcel Holtmann
2020-03-23 7:28 ` [PATCH v1 2/2] Bluetooth: btusb: Read the supported features of Microsoft vendor extension Miao-chen Chou
2020-03-23 17:30 ` kbuild test robot [this message]
2020-03-23 18:05 ` Marcel Holtmann
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=202003240100.nVNDVhCu%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mcchou@chromium.org \
/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).