All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Luciano Coelho <luciano.coelho@nokia.com>
Cc: ext Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wl1271: fix compiler warnings on 64 bit archs
Date: Tue, 11 Aug 2009 15:15:18 -0400	[thread overview]
Message-ID: <20090811191518.GI2634@tuxdriver.com> (raw)
In-Reply-To: <4A81BB47.2020607@nokia.com>

On Tue, Aug 11, 2009 at 09:41:11PM +0300, Luciano Coelho wrote:
> ext Stephen Rothwell wrote:
>> Hi Luciano,
>>
>> On Tue, 11 Aug 2009 11:58:27 +0300 Luciano Coelho <luciano.coelho@nokia.com> wrote:
>>   
>>> +++ b/drivers/net/wireless/wl12xx/wl1271_boot.c
>>> @@ -100,8 +100,8 @@ static int wl1271_boot_upload_firmware_chunk(struct wl1271 *wl, void *buf,
>>>   	wl1271_debug(DEBUG_BOOT, "starting firmware upload");
>>>  -	wl1271_debug(DEBUG_BOOT, "fw_data_len %d chunk_size %d", 
>>> fw_data_len,
>>> -		CHUNK_SIZE);
>>> +	wl1271_debug(DEBUG_BOOT, "fw_data_len %d chunk_size %d",
>>> +		     (u32) fw_data_len, CHUNK_SIZE);
>>>     
>>
>> fw_data_len is a size_t and so should be printed with %zd.
>>
>>   
>>> @@ -148,7 +148,7 @@ static int wl1271_boot_upload_firmware_chunk(struct wl1271 *wl, void *buf,
>>>  	addr = dest + chunk_num * CHUNK_SIZE;
>>>  	p = buf + chunk_num * CHUNK_SIZE;
>>>  	wl1271_debug(DEBUG_BOOT, "uploading fw last chunk (%d B) 0x%p to 0x%x",
>>> -		     fw_data_len % CHUNK_SIZE, p, addr);
>>> +		     (u32) fw_data_len % CHUNK_SIZE, p, addr);
>>>     
>>
>> ditto.
>>   
>
> Thanks! I didn't know about the z length modifier for printf (everyday  
> learning something new!), I should have checked the manpage.  I'll fix  
> this and send v2 of my patch.

I've got it fixed-up already...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  parent reply	other threads:[~2009-08-11 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11  8:58 [PATCH] wl1271: fix compiler warnings on 64 bit archs Luciano Coelho
2009-08-11  8:58 ` Luciano Coelho
2009-08-11 10:07 ` Stephen Rothwell
2009-08-11 18:41   ` Luciano Coelho
2009-08-11 18:45     ` Randy Dunlap
2009-08-11 19:15     ` John W. Linville [this message]
2009-08-11 19:43       ` Luciano Coelho

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=20090811191518.GI2634@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@nokia.com \
    --cc=sfr@canb.auug.org.au \
    /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.