From: kbuild test robot <lkp@intel.com>
To: Raghuram Hegde <raghuram.hegde@intel.com>
Cc: kbuild-all@01.org, linux-bluetooth@vger.kernel.org,
raghuram.hegde@intel.com, chethan.tumkur.narayan@intel.com,
sukumar.ghorai@intel.com, amit.k.bag@intel.com
Subject: Re: [PATCH 1/2] Bluetooth: btintel: Add platform device for rfkill signal
Date: Tue, 21 Aug 2018 22:54:49 +0800 [thread overview]
Message-ID: <201808212229.4VJcNtpA%fengguang.wu@intel.com> (raw)
In-Reply-To: <1534844080-31240-1-git-send-email-raghuram.hegde@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]
Hi Sukumar,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bluetooth/master]
[also build test WARNING on v4.18 next-20180821]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Raghuram-Hegde/Bluetooth-btintel-Add-platform-device-for-rfkill-signal/20180821-195829
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git master
config: arm-multi_v7_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=arm
All warnings (new ones prefixed by >>):
In file included from drivers/bluetooth/hci_ldisc.c:49:0:
drivers/bluetooth/btintel.h: In function 'btintel_reset_bt':
>> drivers/bluetooth/btintel.h:177:9: warning: 'return' with a value, in function returning void
return -EOPNOTSUPP;
^
drivers/bluetooth/btintel.h:175:20: note: declared here
static inline void btintel_reset_bt(struct hci_dev *hdev, unsigned char code)
^~~~~~~~~~~~~~~~
vim +/return +177 drivers/bluetooth/btintel.h
174
175 static inline void btintel_reset_bt(struct hci_dev *hdev, unsigned char code)
176 {
> 177 return -EOPNOTSUPP;
178 }
179
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 43451 bytes --]
next prev parent reply other threads:[~2018-08-21 14:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 9:34 [PATCH 1/2] Bluetooth: btintel: Add platform device for rfkill signal Raghuram Hegde
2018-08-21 9:34 ` [PATCH 2/2] Bluletooth: Add hardware reset callback to reset intel bluetooth chip Raghuram Hegde
2018-08-21 14:14 ` Marcel Holtmann
2018-08-21 14:42 ` chethan tn
2018-08-21 14:13 ` [PATCH 1/2] Bluetooth: btintel: Add platform device for rfkill signal Marcel Holtmann
2018-08-21 14:58 ` chethan tn
2018-08-21 15:09 ` Marcel Holtmann
2018-09-11 4:45 ` chethan tn
2018-09-11 5:13 ` Hegde, Raghuram
2018-09-27 10:44 ` Marcel Holtmann
2018-08-21 14:54 ` kbuild test robot [this message]
2018-08-21 16:55 ` kbuild test robot
2018-08-21 16:55 ` [PATCH] Bluetooth: btintel: fix ptr_ret.cocci warnings kbuild test robot
2018-08-21 20:20 ` Marcel Holtmann
2018-08-22 1:52 ` [kbuild-all] " Li, Philip
2018-08-22 2:00 ` Fengguang Wu
2018-08-22 1:59 ` Fengguang Wu
2018-08-22 6:08 ` Marcel Holtmann
2018-08-22 6:35 ` Fengguang Wu
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=201808212229.4VJcNtpA%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=amit.k.bag@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=raghuram.hegde@intel.com \
--cc=sukumar.ghorai@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).