From: Randy Dunlap <rdunlap@infradead.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arend van Spriel <arend@broadcom.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
brcm80211-dev-list@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH -next] wireless: brcmfmac: fix printk format warning
Date: Tue, 13 Nov 2012 07:55:18 -0800 [thread overview]
Message-ID: <50A26D66.4060603@infradead.org> (raw)
In-Reply-To: <1351798279.17469.0.camel@jlt4.sipsolutions.net>
On 11/01/2012 12:31 PM, Johannes Berg wrote:
> On Thu, 2012-11-01 at 19:01 +0100, Arend van Spriel wrote:
>> On 11/01/2012 06:43 PM, Randy Dunlap wrote:
>>> From: Randy Dunlap <rdunlap@infradead.org>
>>>
>>> Fix printk format warning for ssid_len, which is a size_t:
>>>
>>> drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c:3941:2: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
>>>
>>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>>> Cc: brcm80211-dev-list@broadcom.com
>>
>>
>> We actually have a patch ready for that with credit to people who
>> reported it. We can add you to that list ;-)
>
> Which you've been sitting on for WAY too long already :)
ping Arend.
Please have your patch included in linux-next builds. thanks.
--
~Randy
next prev parent reply other threads:[~2012-11-13 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 5:36 linux-next: Tree for Nov 1 Stephen Rothwell
2012-11-01 17:18 ` linux-next: Tree for Nov 1 (xen) Randy Dunlap
2012-11-01 21:57 ` Konrad Rzeszutek Wilk
[not found] ` <20121101163622.129b59967d2ee76e6946874a-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2012-11-01 17:43 ` [PATCH -next] wireless: brcmfmac: fix printk format warning Randy Dunlap
2012-11-01 18:01 ` Arend van Spriel
2012-11-01 19:31 ` Johannes Berg
2012-11-01 20:51 ` Arend van Spriel
2012-11-01 21:14 ` Randy Dunlap
2012-11-13 15:55 ` Randy Dunlap [this message]
2012-11-13 21:52 ` Arend van Spriel
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=50A26D66.4060603@infradead.org \
--to=rdunlap@infradead.org \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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).