From: kernel test robot <lkp@intel.com>
To: Joseph Hwang <josephsih@chromium.org>,
linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, pali@kernel.org
Cc: kbuild-all@lists.01.org, josephsih@google.com,
chromeos-bluetooth-upstreaming@chromium.org,
Joseph Hwang <josephsih@chromium.org>,
Archie Pusaka <apusaka@chromium.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v5 2/5] Bluetooth: aosp: surface AOSP quality report through mgmt
Date: Thu, 26 May 2022 04:15:43 +0800 [thread overview]
Message-ID: <202205260445.F8Xkowrk-lkp@intel.com> (raw)
In-Reply-To: <20220525184510.v5.2.I2015b42d2d0a502334c9c3a2983438b89716d4f0@changeid>
Hi Joseph,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bluetooth-next/master]
[also build test WARNING on net-next/master net/master v5.18 next-20220525]
[cannot apply to bluetooth/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/intel-lab-lkp/linux/commits/Joseph-Hwang/Bluetooth-mgmt-add-MGMT_OP_SET_QUALITY_REPORT-for-quality-report/20220525-184722
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220526/202205260445.F8Xkowrk-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-1) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-14-g5a0004b5-dirty
# https://github.com/intel-lab-lkp/linux/commit/0121eca73c0352b9ac4bc289609b218c0d0fb69e
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Joseph-Hwang/Bluetooth-mgmt-add-MGMT_OP_SET_QUALITY_REPORT-for-quality-report/20220525-184722
git checkout 0121eca73c0352b9ac4bc289609b218c0d0fb69e
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash net/bluetooth/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
net/bluetooth/hci_event.c:338:15: sparse: sparse: restricted __le16 degrades to integer
>> net/bluetooth/hci_event.c:4275:3: sparse: sparse: symbol 'evt_prefixes' was not declared. Should it be static?
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
include/net/bluetooth/hci.h:2494:47: sparse: sparse: array of flexible structures
include/net/bluetooth/hci.h:2580:43: sparse: sparse: array of flexible structures
vim +/evt_prefixes +4275 net/bluetooth/hci_event.c
4262
4263 /* Every distinct vendor specification must have a well-defined vendor
4264 * event prefix to determine if a vendor event meets the specification.
4265 * Some vendor prefixes are fixed values while some other vendor prefixes
4266 * are only available at run time.
4267 */
4268 struct ext_vendor_event_prefix {
4269 /* Some vendor prefixes are variable length. For convenience,
4270 * the prefix in struct ext_vendor_prefix is in little endian.
4271 */
4272 struct ext_vendor_prefix *
4273 (*get_ext_vendor_prefix)(struct hci_dev *hdev);
4274 void (*vendor_func)(struct hci_dev *hdev, struct sk_buff *skb);
> 4275 } evt_prefixes[] = {
4276 { aosp_get_ext_prefix, aosp_vendor_evt },
4277 { msft_get_ext_prefix, msft_vendor_evt },
4278
4279 /* end with a null entry */
4280 {},
4281 };
4282
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-05-25 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 10:45 [PATCH v5 1/5] Bluetooth: mgmt: add MGMT_OP_SET_QUALITY_REPORT for quality report Joseph Hwang
2022-05-25 10:45 ` [PATCH v5 2/5] Bluetooth: aosp: surface AOSP quality report through mgmt Joseph Hwang
2022-05-25 20:15 ` kernel test robot [this message]
2022-05-25 10:45 ` [PATCH v5 3/5] Bluetooth: hci_event: Add vendor functions to handle vendor events Joseph Hwang
2022-05-25 10:45 ` [PATCH v5 5/5] Bluetooth: let HCI_QUALITY_REPORT persist over adapter power cycle Joseph Hwang
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=202205260445.F8Xkowrk-lkp@intel.com \
--to=lkp@intel.com \
--cc=apusaka@chromium.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=josephsih@chromium.org \
--cc=josephsih@google.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pali@kernel.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).