From: Dan Carpenter <dan.carpenter@oracle.com>
To: kbuild@lists.01.org, Archie Pusaka <apusaka@google.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>
Cc: lkp@intel.com, kbuild-all@lists.01.org,
CrosBT Upstreaming <chromeos-bluetooth-upstreaming@chromium.org>,
Archie Pusaka <apusaka@chromium.org>,
Miao-chen Chou <mcchou@chromium.org>,
Yun-Hao Chung <howardchung@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] Bluetooth: advmon offload MSFT remove monitor
Date: Tue, 15 Dec 2020 22:03:54 +0300 [thread overview]
Message-ID: <20201215190354.GI2809@kadam> (raw)
In-Reply-To: <20201215163106.v2.3.I2bdb3d9953a91dc7865da6e57166260b3a75c146@changeid>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
Hi Archie,
url: https://github.com/0day-ci/linux/commits/Archie-Pusaka/MSFT-offloading-support-for-advertisement-monitor/20201215-163858
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
config: i386-randconfig-m021-20201215 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch warnings:
net/bluetooth/msft.h:45 msft_remove_monitor() warn: signedness bug returning '(-95)'
vim +45 net/bluetooth/msft.h
d8ca4cbc63c57c8 Archie Pusaka 2020-12-15 41 static inline bool msft_remove_monitor(struct hci_dev *hdev,
^^^^
d8ca4cbc63c57c8 Archie Pusaka 2020-12-15 42 struct adv_monitor *monitor,
d8ca4cbc63c57c8 Archie Pusaka 2020-12-15 43 u16 handle)
d8ca4cbc63c57c8 Archie Pusaka 2020-12-15 44 {
d8ca4cbc63c57c8 Archie Pusaka 2020-12-15 @45 return -EOPNOTSUPP;
^^^^^^^^^^^^^^^^^^^
change this to return false?
d8ca4cbc63c57c8 Archie Pusaka 2020-12-15 46 }
---
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: 32738 bytes --]
next prev parent reply other threads:[~2020-12-15 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 8:31 [PATCH v2 0/5] MSFT offloading support for advertisement monitor Archie Pusaka
2020-12-15 8:31 ` [PATCH v2 1/5] Bluetooth: advmon offload MSFT add rssi support Archie Pusaka
2020-12-15 9:16 ` MSFT offloading support for advertisement monitor bluez.test.bot
2020-12-15 8:31 ` [PATCH v2 2/5] Bluetooth: advmon offload MSFT add monitor Archie Pusaka
2020-12-15 8:31 ` [PATCH v2 3/5] Bluetooth: advmon offload MSFT remove monitor Archie Pusaka
2020-12-15 19:03 ` Dan Carpenter [this message]
2020-12-16 4:33 ` Archie Pusaka
2020-12-15 8:32 ` [PATCH v2 4/5] Bluetooth: advmon offload MSFT handle controller reset Archie Pusaka
2020-12-15 8:32 ` [PATCH v2 5/5] Bluetooth: advmon offload MSFT handle filter enablement Archie Pusaka
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=20201215190354.GI2809@kadam \
--to=dan.carpenter@oracle.com \
--cc=apusaka@chromium.org \
--cc=apusaka@google.com \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=howardchung@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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).