All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [bluetooth:master 239/247] net/bluetooth/hci_event.c:886:3: warning: format '%ld' expects argument o
Date: Fri, 28 Sep 2012 01:22:14 +0000	[thread overview]
Message-ID: <20120928012214.GF5522@localhost> (raw)

Hi Gustavo,

FYI, there are new compile warnings show up in

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
head:   29d8a5909bba10accb82eb805c884a2943d7710f
commit: 392f44d3e7894f6fe314b85b4a1611b7b1d98226 [239/247] Bluetooth: Fix two warnings in BT_DBG
config: powerpc-wii_defconfig

All warnings:

net/bluetooth/hci_event.c: In function 'hci_cc_read_local_amp_assoc':
net/bluetooth/hci_event.c:886:3: warning: format '%ld' expects argument of type 'long int', but argument 2 has type 'size_t' [-Wformat]
net/bluetooth/hci_event.c:886:3: warning: format '%ld' expects argument of type 'long int', but argument 3 has type 'size_t' [-Wformat]
--
net/bluetooth/a2mp.c: In function 'a2mp_getampassoc_rsp':
net/bluetooth/a2mp.c:386:2: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'unsigned int' [-Wformat]

vim +886 net/bluetooth/hci_event.c

903e4541 (Andrei Emeltchenko 2012-09-27  870) static void hci_cc_read_local_amp_assoc(struct hci_dev *hdev,
903e4541 (Andrei Emeltchenko 2012-09-27  871) 					struct sk_buff *skb)
903e4541 (Andrei Emeltchenko 2012-09-27  872) {
903e4541 (Andrei Emeltchenko 2012-09-27  873) 	struct hci_rp_read_local_amp_assoc *rp = (void *) skb->data;
903e4541 (Andrei Emeltchenko 2012-09-27  874) 	struct amp_assoc *assoc = &hdev->loc_assoc;
903e4541 (Andrei Emeltchenko 2012-09-27  875) 	size_t rem_len, frag_len;
903e4541 (Andrei Emeltchenko 2012-09-27  876) 
903e4541 (Andrei Emeltchenko 2012-09-27  877) 	BT_DBG("%s status 0x%2.2x", hdev->name, rp->status);
903e4541 (Andrei Emeltchenko 2012-09-27  878) 
903e4541 (Andrei Emeltchenko 2012-09-27  879) 	if (rp->status)
903e4541 (Andrei Emeltchenko 2012-09-27  880) 		goto a2mp_rsp;
903e4541 (Andrei Emeltchenko 2012-09-27  881) 
903e4541 (Andrei Emeltchenko 2012-09-27  882) 	frag_len = skb->len - sizeof(*rp);
903e4541 (Andrei Emeltchenko 2012-09-27  883) 	rem_len = __le16_to_cpu(rp->rem_len);
903e4541 (Andrei Emeltchenko 2012-09-27  884) 
903e4541 (Andrei Emeltchenko 2012-09-27  885) 	if (rem_len > frag_len) {
392f44d3 (Gustavo Padovan    2012-09-27 @886) 		BT_DBG("frag_len %ld rem_len %ld", frag_len, rem_len);
903e4541 (Andrei Emeltchenko 2012-09-27  887) 
903e4541 (Andrei Emeltchenko 2012-09-27  888) 		memcpy(assoc->data + assoc->offset, rp->frag, frag_len);
903e4541 (Andrei Emeltchenko 2012-09-27  889) 		assoc->offset += frag_len;
903e4541 (Andrei Emeltchenko 2012-09-27  890) 
903e4541 (Andrei Emeltchenko 2012-09-27  891) 		/* Read other fragments */
903e4541 (Andrei Emeltchenko 2012-09-27  892) 		amp_read_loc_assoc_frag(hdev, rp->phy_handle);
903e4541 (Andrei Emeltchenko 2012-09-27  893) 
903e4541 (Andrei Emeltchenko 2012-09-27  894) 		return;

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu, Yuanhan Liu                              Intel Corporation

                 reply	other threads:[~2012-09-28  1:22 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=20120928012214.GF5522@localhost \
    --to=fengguang.wu@intel.com \
    --cc=kernel-janitors@vger.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 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.