From: kernel test robot <lkp@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>, linux-bluetooth@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH] Bluetooth: Add support for reading AOSP vendor capabilities
Date: Wed, 7 Apr 2021 02:41:43 +0800 [thread overview]
Message-ID: <202104070205.ETAFMlD5-lkp@intel.com> (raw)
In-Reply-To: <20210406133632.241599-1-marcel@holtmann.org>
[-- Attachment #1: Type: text/plain, Size: 3439 bytes --]
Hi Marcel,
I love your patch! Yet something to improve:
[auto build test ERROR on bluetooth-next/master]
[also build test ERROR on v5.12-rc6 next-20210406]
[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/Marcel-Holtmann/Bluetooth-Add-support-for-reading-AOSP-vendor-capabilities/20210406-213836
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
config: m68k-randconfig-r023-20210406 (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/71e8a18c61c482db0f170ec897450ba76c18b7ec
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Marcel-Holtmann/Bluetooth-Add-support-for-reading-AOSP-vendor-capabilities/20210406-213836
git checkout 71e8a18c61c482db0f170ec897450ba76c18b7ec
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
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 >>):
In file included from net/bluetooth/hci_core.c:47:
>> net/bluetooth/aosp.h:13:20: error: static declaration of 'msft_do_open' follows non-static declaration
13 | static inline void msft_do_open(struct hci_dev *hdev) {}
| ^~~~~~~~~~~~
In file included from net/bluetooth/hci_core.c:46:
net/bluetooth/msft.h:16:6: note: previous declaration of 'msft_do_open' was here
16 | void msft_do_open(struct hci_dev *hdev);
| ^~~~~~~~~~~~
In file included from net/bluetooth/hci_core.c:47:
>> net/bluetooth/aosp.h:14:20: error: static declaration of 'msft_do_close' follows non-static declaration
14 | static inline void msft_do_close(struct hci_dev *hdev) {}
| ^~~~~~~~~~~~~
In file included from net/bluetooth/hci_core.c:46:
net/bluetooth/msft.h:17:6: note: previous declaration of 'msft_do_close' was here
17 | void msft_do_close(struct hci_dev *hdev);
| ^~~~~~~~~~~~~
net/bluetooth/hci_core.c: In function 'hci_dev_do_open':
>> net/bluetooth/hci_core.c:1590:2: error: implicit declaration of function 'aosp_do_open'; did you mean 'msft_do_open'? [-Werror=implicit-function-declaration]
1590 | aosp_do_open(hdev);
| ^~~~~~~~~~~~
| msft_do_open
net/bluetooth/hci_core.c: In function 'hci_dev_do_close':
>> net/bluetooth/hci_core.c:1787:2: error: implicit declaration of function 'aosp_do_close'; did you mean 'msft_do_close'? [-Werror=implicit-function-declaration]
1787 | aosp_do_close(hdev);
| ^~~~~~~~~~~~~
| msft_do_close
cc1: some warnings being treated as errors
vim +/msft_do_open +13 net/bluetooth/aosp.h
12
> 13 static inline void msft_do_open(struct hci_dev *hdev) {}
> 14 static inline void msft_do_close(struct hci_dev *hdev) {}
15
---
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: 27044 bytes --]
prev parent reply other threads:[~2021-04-06 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 13:36 [PATCH] Bluetooth: Add support for reading AOSP vendor capabilities Marcel Holtmann
2021-04-06 17:41 ` kernel test robot
2021-04-06 18:41 ` kernel test robot [this message]
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=202104070205.ETAFMlD5-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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