From: kernel test robot <lkp@intel.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH] Bluetooth: Fix handling of LE Enhanced Connection Complete
Date: Fri, 6 Aug 2021 05:53:57 +0800 [thread overview]
Message-ID: <202108060556.68YxYcPX-lkp@intel.com> (raw)
In-Reply-To: <20210805190251.507081-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2643 bytes --]
Hi Luiz,
I love your patch! Yet something to improve:
[auto build test ERROR on bluetooth-next/master]
[also build test ERROR on bluetooth/master v5.14-rc4 next-20210805]
[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/0day-ci/linux/commits/Luiz-Augusto-von-Dentz/Bluetooth-Fix-handling-of-LE-Enhanced-Connection-Complete/20210806-030407
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
config: ia64-randconfig-s031-20210804 (attached as .config)
compiler: ia64-linux-gcc (GCC) 10.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-348-gf0e6938b-dirty
# https://github.com/0day-ci/linux/commit/3d908e1b6ece1fa2fb113bbc447b288f71245fd4
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Luiz-Augusto-von-Dentz/Bluetooth-Fix-handling-of-LE-Enhanced-Connection-Complete/20210806-030407
git checkout 3d908e1b6ece1fa2fb113bbc447b288f71245fd4
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=ia64 SHELL=/bin/bash net/bluetooth/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
net/bluetooth/hci_event.c: In function 'hci_le_conn_complete_evt':
>> net/bluetooth/hci_event.c:5380:12: error: 'struct hci_ev_le_conn_complete' has no member named 'local_rpa'
5380 | &ev->local_rpa, ev->role, le16_to_cpu(ev->handle),
| ^~
vim +5380 net/bluetooth/hci_event.c
5372
5373 static void hci_le_conn_complete_evt(struct hci_dev *hdev, struct sk_buff *skb)
5374 {
5375 struct hci_ev_le_conn_complete *ev = (void *) skb->data;
5376
5377 BT_DBG("%s status 0x%2.2x", hdev->name, ev->status);
5378
5379 le_conn_complete_evt(hdev, ev->status, &ev->bdaddr, ev->bdaddr_type,
> 5380 &ev->local_rpa, ev->role, le16_to_cpu(ev->handle),
5381 le16_to_cpu(ev->interval),
5382 le16_to_cpu(ev->latency),
5383 le16_to_cpu(ev->supervision_timeout));
5384 }
5385
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31576 bytes --]
next prev parent reply other threads:[~2021-08-05 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 19:02 [PATCH] Bluetooth: Fix handling of LE Enhanced Connection Complete Luiz Augusto von Dentz
2021-08-05 21:53 ` kernel test robot [this message]
2021-08-05 23:04 ` kernel test robot
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=202108060556.68YxYcPX-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox