public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime•net>
To: Randy Dunlap <rdunlap@xenotime•net>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
	Marco Stornelli <marco.stornelli@gmail•com>,
	Kees Cook <keescook@chromium•org>,
	Andrew Morton <akpm@linux-foundation•org>
Subject: Re: [PATCH -next] pstore: fix printk format warning in ram.c
Date: Thu, 21 Jun 2012 17:04:57 -0700	[thread overview]
Message-ID: <4FE3B6A9.60109@xenotime.net> (raw)
In-Reply-To: <4FDB8AB8.6060703@xenotime.net>

Greg,
This patch is still needed in linux-next.....


also:
Acked-by: Kees Cook <keescook@chromium•org>



On 06/15/2012 12:19 PM, Randy Dunlap wrote:

> From: Randy Dunlap <rdunlap@xenotime•net>
> 
> Fix printk format warning (on i386) in pstore:
> 
> fs/pstore/ram.c:378:3: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'size_t'
> 
> Signed-off-by: Randy Dunlap <rdunlap@xenotime•net>
> ---
>  fs/pstore/ram.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-next-20120615.orig/fs/pstore/ram.c
> +++ linux-next-20120615/fs/pstore/ram.c
> @@ -375,7 +375,7 @@ static int __init ramoops_probe(struct p
>  		goto fail_init_cprz;
>  
>  	if (!cxt->przs && !cxt->cprz) {
> -		pr_err("memory size too small, minimum is %lu\n",
> +		pr_err("memory size too small, minimum is %zu\n",
>  			cxt->console_size + cxt->record_size);
>  		goto fail_cnt;
>  	}
> 



-- 
~Randy

      parent reply	other threads:[~2012-06-22  0:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15  4:33 linux-next: Tree for Jun 15 Stephen Rothwell
2012-06-15  6:52 ` error: implicit declarations of BUG/BUG_ON/WARN_ON/WARN_ON_ONCE Fengguang Wu
2012-06-15 16:27   ` Randy Dunlap
2012-06-18 16:54     ` Randy Dunlap
2012-06-22  7:13       ` Fengguang Wu
2012-06-25  2:53         ` Paul Mundt
2012-06-25  4:20           ` Fengguang Wu
2012-06-25  4:23             ` Randy Dunlap
2012-06-25  4:38               ` Fengguang Wu
2012-06-25  4:39                 ` Randy Dunlap
2012-06-25  4:55                   ` Fengguang Wu
2012-06-25  5:05                     ` Randy Dunlap
2012-06-25  4:54               ` Paul Mundt
2012-06-15 19:19 ` [PATCH -next] pstore: fix printk format warning in ram.c Randy Dunlap
2012-06-15 19:32   ` Kees Cook
2012-06-22  0:04   ` Randy Dunlap [this message]

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=4FE3B6A9.60109@xenotime.net \
    --to=rdunlap@xenotime$(echo .)net \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=keescook@chromium$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=marco.stornelli@gmail$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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