From: Greg KH <greg@kroah.com>
To: Roland Vossen <rvossen@broadcom.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"gregkh@suse.de" <gregkh@suse.de>,
driverdevel <devel@driverdev.osuosl.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Arend Van Spriel <arend@broadcom.com>
Subject: Re: [PATCH -next] staging/brcm80211: fix printk format warnings
Date: Wed, 2 Mar 2011 16:02:29 -0500 [thread overview]
Message-ID: <20110302210229.GB20522@kroah.com> (raw)
In-Reply-To: <4D6E4F18.4060505@broadcom.com>
On Wed, Mar 02, 2011 at 03:07:20PM +0100, Roland Vossen wrote:
> >drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c:1379: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
> >drivers/staging/brcm80211/sys/wl_mac80211.c:1827: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
> >drivers/staging/brcm80211/sys/wl_mac80211.c:1832: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
> >
> >Signed-off-by: Randy Dunlap<randy.dunlap@oracle.com>
>
> Acked-by: Roland Vossen<rvossen@broadcom.com>
Please note you need a ' ' before the '<' character. I'm getting tired
of adding it myself :)
thanks,
greg k-h
next prev parent reply other threads:[~2011-03-02 21:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 7:11 linux-next: Tree for March 1 Stephen Rothwell
2011-03-01 18:49 ` linux-next: Tree for March 1 (staging/winbond) Randy Dunlap
2011-03-01 19:10 ` Pekka Enberg
2011-03-01 19:19 ` Randy Dunlap
2011-03-01 19:35 ` Pekka Enberg
2011-03-01 19:39 ` Randy Dunlap
2011-03-01 20:05 ` Pekka Enberg
2011-03-01 20:07 ` Greg KH
2011-03-02 0:29 ` [PATCH -next] staging/brcm80211: fix printk format warnings Randy Dunlap
2011-03-02 14:07 ` Roland Vossen
2011-03-02 21:02 ` Greg KH [this message]
2011-03-02 21:05 ` Greg KH
2011-03-02 23:36 ` Stephen Rothwell
2011-03-03 7:20 ` Stanislav Fomichev
2011-03-03 16:08 ` Randy Dunlap
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=20110302210229.GB20522@kroah.com \
--to=greg@kroah.com \
--cc=arend@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rvossen@broadcom.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).