From: Kalle Valo <kalle.valo@nokia.com>
To: ext Bob Copeland <me@bobcopeland.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: linux-next: wireless tree build warning
Date: Mon, 04 May 2009 09:48:49 +0300 [thread overview]
Message-ID: <87y6tdbbxq.fsf@nokia.com> (raw)
In-Reply-To: <20090501123339.GA4917@hash.localnet> (ext Bob Copeland's message of "Fri\, 1 May 2009 14\:33\:39 +0200")
ext Bob Copeland <me@bobcopeland.com> writes:
> On Fri, May 01, 2009 at 01:35:39PM +1000, Stephen Rothwell wrote:
>> Hi John,
>>
>> Today's linux-next build (x86_64 allmodconfig) produced these warnings:
>
> Thanks -- John, this should fix:
>
> From 2c6ef7ec3a3b46601597615cf9e40b2a0c9f2f72 Mon Sep 17 00:00:00 2001
> From: Bob Copeland <bob@hash.(none)>
> Date: Fri, 1 May 2009 08:20:07 -0400
> Subject: [PATCH] wl12xx: correct printk format warnings
>
> Fixes warnings:
> drivers/net/wireless/wl12xx/main.c:87: warning: int format, different
> type arg (arg 2)
> drivers/net/wireless/wl12xx/main.c: In function `wl12xx_fetch_nvs':
> drivers/net/wireless/wl12xx/main.c:125: warning: int format, different
> type arg (arg 2)
> drivers/net/wireless/wl12xx/wl1251.c: In function 'wl1251_upload_firmware':
> drivers/net/wireless/wl12xx/wl1251.c:94: warning: int format, different
> type arg (arg 2)
> drivers/net/wireless/wl12xx/wl1251.c:141: warning: int format, different
> type arg (arg 2)
>
> Signed-off-by: Bob Copeland <me@bobcopeland.com>
Thanks.
Acked-by: Kalle Valo <kalle.valo@nokia.com>
--
Kalle Valo
next prev parent reply other threads:[~2009-05-04 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 3:35 linux-next: wireless tree build warning Stephen Rothwell
2009-05-01 12:33 ` Bob Copeland
2009-05-04 6:48 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-01 3:59 Stephen Rothwell
2009-07-28 4:31 Stephen Rothwell
2009-04-22 4:45 Stephen Rothwell
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=87y6tdbbxq.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.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 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).