From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [chrome-os:chromeos-5.4 16/51] net/bluetooth/hci_le_splitter.c:609:3: warning: format '%u' expects argument of type 'unsigned int', but argument 3 has type 'size_t'
Date: Fri, 21 Feb 2020 00:27:27 +0800 [thread overview]
Message-ID: <202002210022.Cc6Fxw1H%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.4
head: 18103a374146f0808d20c7e8fed1880ccafc9fb0
commit: 42d50b012632da5f5cd873a4db4e53beb907e15a [16/51] Revert "FIXUP: CHROMIUM: Bluetooth: Add BT splitter"
config: x86_64-randconfig-a003-20200220 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.2-10+deb8u1) 4.9.2
reproduce:
git checkout 42d50b012632da5f5cd873a4db4e53beb907e15a
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
net/bluetooth/hci_le_splitter.c: In function 'hci_le_splitter_enq_packet':
>> net/bluetooth/hci_le_splitter.c:609:3: warning: format '%u' expects argument of type 'unsigned int', but argument 3 has type 'size_t' [-Wformat=]
pr_err("enqueue failed - not enough space to enqueue %u bytes over %u\n",
^
vim +609 net/bluetooth/hci_le_splitter.c
602
603 /* always takes ownership of skb */
604 static void hci_le_splitter_enq_packet(struct sk_buff *skb)
605 {
606 mutex_lock(&usr_msg_q_lock);
607 if (MAX_RX_QUEUE_SZ - usr_msg_q_len < skb->len) {
608
> 609 pr_err("enqueue failed - not enough space to enqueue %u bytes over %u\n",
610 skb->len, usr_msg_q_len);
611 kfree_skb(skb);
612 } else {
613 usr_msg_q_len += skb->len;
614 skb_queue_tail(&usr_msg_q, skb);
615 }
616 mutex_unlock(&usr_msg_q_lock);
617
618 /* wake up userspace in either case as we have data */
619 wake_up_interruptible(&usr_msg_wait_q);
620 }
621
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 39238 bytes --]
reply other threads:[~2020-02-20 16:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202002210022.Cc6Fxw1H%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.