From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Herbert Xu <herbert@gondor.hengli.com.au>,
linux-crypto@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] asymmetric keys: fix printk format warning
Date: Thu, 04 Oct 2012 12:48:27 +0930 [thread overview]
Message-ID: <874nma3oxo.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20121004090806.70274213735de74211f4334d@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> [Lets also cc Rusty who committed the patch ...]
>
> On Wed, 03 Oct 2012 16:04:46 -0700 Randy Dunlap <rdunlap@xenotime.net> wrote:
>>
>> From: Randy Dunlap <rdunlap@xenotime.net>
>>
>> Fix printk format warning in x509_cert_parser.c:
>>
>> crypto/asymmetric_keys/x509_cert_parser.c: In function 'x509_note_OID':
>> crypto/asymmetric_keys/x509_cert_parser.c:113:3: warning: format '%zu' expects type 'size_t', but argument 2 has type 'long unsigned int'
>>
>> Builds cleanly on i386 and x86_64.
Thanks, applied.
Rusty.
next prev parent reply other threads:[~2012-10-04 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 7:30 linux-next: Tree for Oct 3 Stephen Rothwell
2012-10-03 21:50 ` [PATCH -next] infiniband: fix ipoib build error when IPOIB_CM is not enabled Randy Dunlap
2012-10-03 23:04 ` [PATCH -next] asymmetric keys: fix printk format warning Randy Dunlap
2012-10-03 23:08 ` Stephen Rothwell
2012-10-04 3:18 ` Rusty Russell [this message]
2012-10-03 23:31 ` linux-next: Tree for Oct 3 (mfd/syscon) Randy Dunlap
2012-10-15 8:32 ` Dong Aisheng
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=874nma3oxo.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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