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,
chromeos-bluetooth-upstreaming@chromium.org,
josephsih@google.com, Joseph Hwang <josephsih@chromium.org>,
Archie Pusaka <apusaka@chromium.org>,
Jakub Kicinski <kuba@kernel.org>,
Johan Hedberg <johan.hedberg@gmail.com>
Subject: Re: [PATCH v1 2/2] Bluetooth: btintel: surface Intel telemetry events through mgmt
Date: Sat, 22 Jan 2022 02:30:02 +0800 [thread overview]
Message-ID: <202201220238.tZ1BfUpc-lkp@intel.com> (raw)
In-Reply-To: <20220121192152.v1.2.I63681490281b2392aa1ac05dff91a126394ab649@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 next-20220121]
[cannot apply to net-next/master net/master bluetooth/master v5.16]
[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/Joseph-Hwang/Bluetooth-aosp-surface-AOSP-quality-report-through-mgmt/20220121-192436
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
config: ia64-randconfig-r035-20220121 (https://download.01.org/0day-ci/archive/20220122/202201220238.tZ1BfUpc-lkp@intel.com/config)
compiler: ia64-linux-gcc (GCC) 11.2.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/9484eb7f87f7c8759b6fd7eec9d431c375b97432
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Joseph-Hwang/Bluetooth-aosp-surface-AOSP-quality-report-through-mgmt/20220121-192436
git checkout 9484eb7f87f7c8759b6fd7eec9d431c375b97432
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=ia64 SHELL=/bin/bash drivers/bluetooth/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from arch/ia64/include/asm/pgtable.h:153,
from include/linux/pgtable.h:6,
from arch/ia64/include/asm/uaccess.h:40,
from include/linux/uaccess.h:11,
from include/linux/sched/task.h:11,
from include/linux/sched/signal.h:9,
from include/linux/rcuwait.h:6,
from include/linux/percpu-rwsem.h:7,
from include/linux/fs.h:33,
from include/linux/poll.h:10,
from include/net/bluetooth/bluetooth.h:28,
from drivers/bluetooth/btintel.c:14:
arch/ia64/include/asm/mmu_context.h: In function 'reload_context':
arch/ia64/include/asm/mmu_context.h:127:48: warning: variable 'old_rr4' set but not used [-Wunused-but-set-variable]
127 | unsigned long rr0, rr1, rr2, rr3, rr4, old_rr4;
| ^~~~~~~
In file included from drivers/bluetooth/btintel.c:14:
drivers/bluetooth/btintel.c: In function 'btintel_pull_quality_report_data':
>> drivers/bluetooth/btintel.c:2680:24: warning: format '%u' expects argument of type 'unsigned int', but argument 3 has type 'long unsigned int' [-Wformat=]
2680 | BT_ERR("Telemetry event length %d too short (at least %u)",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2681 | skb->len, sizeof(struct intel_tlv));
| ~~~~~~~~~~~~~~~~~~~~~~~~
| |
| long unsigned int
include/net/bluetooth/bluetooth.h:199:40: note: in definition of macro 'BT_ERR'
199 | #define BT_ERR(fmt, ...) bt_err(fmt "\n", ##__VA_ARGS__)
| ^~~
drivers/bluetooth/btintel.c:2680:72: note: format string is defined here
2680 | BT_ERR("Telemetry event length %d too short (at least %u)",
| ~^
| |
| unsigned int
| %lu
vim +2680 drivers/bluetooth/btintel.c
2673
2674 bool btintel_pull_quality_report_data(struct sk_buff *skb)
2675 {
2676 skb_pull(skb, sizeof(struct intel_prefix_evt_data));
2677
2678 /* A telemetry event contains at least one intel_tlv subevent. */
2679 if (skb->len < sizeof(struct intel_tlv)) {
> 2680 BT_ERR("Telemetry event length %d too short (at least %u)",
2681 skb->len, sizeof(struct intel_tlv));
2682 return false;
2683 }
2684
2685 return true;
2686 }
2687 EXPORT_SYMBOL_GPL(btintel_pull_quality_report_data);
2688
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2022-01-21 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 11:22 [PATCH v1 1/2] Bluetooth: aosp: surface AOSP quality report through mgmt Joseph Hwang
2022-01-21 11:22 ` [PATCH v1 2/2] Bluetooth: btintel: surface Intel telemetry events " Joseph Hwang
2022-01-21 18:30 ` kernel test robot [this message]
2022-01-21 20:21 ` Marcel Holtmann
2022-01-22 7:31 ` kernel test robot
2022-01-21 11:57 ` [v1,1/2] Bluetooth: aosp: surface AOSP quality report " bluez.test.bot
2022-01-21 20:16 ` [PATCH v1 1/2] " Marcel Holtmann
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=202201220238.tZ1BfUpc-lkp@intel.com \
--to=lkp@intel.com \
--cc=apusaka@chromium.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--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=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--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).