From: "Matti J. Aaltonen" <matti.j.aaltonen@nokia.com>
To: ext Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Jari Vanhala <ext-jari.vanhala@nokia.com>
Subject: Re: mmotm 2010-10-31-21-24 uploaded (drivers/nfc/pn544)
Date: Tue, 02 Nov 2010 09:57:10 +0200 [thread overview]
Message-ID: <1288684630.1603.102.camel@masi.mnp.nokia.com> (raw)
In-Reply-To: <20101101110024.bca61c57.randy.dunlap@oracle.com>
On Mon, 2010-11-01 at 11:00 -0700, ext Randy Dunlap wrote:
> On Sun, 31 Oct 2010 21:25:59 -0700 akpm@linux-foundation.org wrote:
>
> > The mm-of-the-moment snapshot 2010-10-31-21-24 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
> >
> > and will soon be available at
> >
> > git://zen-kernel.org/kernel/mmotm.git
> >
> > It contains the following patches against 2.6.36:
> >
> > nfc-driver-for-nxp-semiconductors-pn544-nfc-chip.patch
>
>
> Use %zd to print ssize_t variables and %zu to print size_t:
>
> drivers/nfc/pn544.c:332: warning: format '%d' expects type 'int', but argument 6 has type 'size_t'
> drivers/nfc/pn544.c:442: warning: format '%d' expects type 'int', but argument 6 has type 'size_t'
Thanks, I'll do that... I'm using Sparse and checkpatch --strict but
neither gave me a warning about that.
Cheers,
Matti
>
>
> Also see Documentation/printk-formats.txt as needed.
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-11-04 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 4:25 mmotm 2010-10-31-21-24 uploaded akpm
2010-11-01 17:55 ` mmotm 2010-10-31-21-24 uploaded (mm/memcontrol) Randy Dunlap
2010-11-01 18:00 ` mmotm 2010-10-31-21-24 uploaded (drivers/nfc/pn544) Randy Dunlap
2010-11-02 7:57 ` Matti J. Aaltonen [this message]
2010-11-04 14:26 ` Jiri Slaby
2010-11-03 16:04 ` mmotm 2010-10-31-21-24 uploaded Randy Dunlap
2010-11-03 19:21 ` Andrew Morton
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=1288684630.1603.102.camel@masi.mnp.nokia.com \
--to=matti.j.aaltonen@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=ext-jari.vanhala@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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
all inboxes | Powered by JetHome®