public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -next/mmotm/resend] kmemtrace: fix printk formats
Date: Fri, 30 Jan 2009 16:12:51 +0100	[thread overview]
Message-ID: <20090130151251.GC27549@elte.hu> (raw)
In-Reply-To: <20090130074645.GA5218@localhost>


* Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro> wrote:

> On Thu, Jan 29, 2009 at 01:49:45PM -0800, Randy Dunlap wrote:
> > Geert Uytterhoeven wrote:
> > > 
> > > %4zu?
> > 
> > Ugh, yes.  Thanks.
> > Here's the updated patch.
> > 
> > -- 
> > From: Randy Dunlap <randy.dunlap@oracle.com>
> > 
> > Fix kmemtrace printk warnings:
> > 
> > kernel/trace/kmemtrace.c:142: warning: format '%4ld' expects type 'long int', but argument 3 has type 'size_t'
> > kernel/trace/kmemtrace.c:147: warning: format '%4ld' expects type 'long int', but argument 3 has type 'size_t'
> > 
> > Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> > cc:      Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
> > ---
> >  kernel/trace/kmemtrace.c |    4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > --- linux-next-20090123.orig/kernel/trace/kmemtrace.c
> > +++ linux-next-20090123/kernel/trace/kmemtrace.c
> > @@ -139,12 +139,12 @@ kmemtrace_print_alloc_compress(struct tr
> >  		return TRACE_TYPE_PARTIAL_LINE;
> >  
> >  	/* Requested */
> > -	ret = trace_seq_printf(s, "%4ld   ", entry->bytes_req);
> > +	ret = trace_seq_printf(s, "%4zu   ", entry->bytes_req);
> >  	if (!ret)
> >  		return TRACE_TYPE_PARTIAL_LINE;
> >  
> >  	/* Allocated */
> > -	ret = trace_seq_printf(s, "%4ld   ", entry->bytes_alloc);
> > +	ret = trace_seq_printf(s, "%4zu   ", entry->bytes_alloc);
> >  	if (!ret)
> >  		return TRACE_TYPE_PARTIAL_LINE;
> >
> 
> I didn't notice this either, thanks.
> 
> Acked-by: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>

Applied to tip/tracing/kmemtrace, thanks!

	Ingo

  reply	other threads:[~2009-01-30 15:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200901291030.n0TAUhRI003046@imap1.linux-foundation.org>
2009-01-29 17:33 ` [PATCH -next/mmotm/resend] kmemtrace: fix printk formats Randy Dunlap
2009-01-29 18:51   ` Ingo Molnar
2009-01-29 21:35   ` Geert Uytterhoeven
2009-01-29 21:49     ` Randy Dunlap
2009-01-30  7:46       ` Eduard - Gabriel Munteanu
2009-01-30 15:12         ` Ingo Molnar [this message]
2009-01-29 17:49 ` mmotm 2009-01-29-02-29 uploaded (wimax) Randy Dunlap
2009-01-29 18:58   ` Inaky Perez-Gonzalez
2009-01-29 19:23     ` Valdis.Kletnieks
2009-01-29 20:41     ` Randy Dunlap
2009-01-29 21:46   ` [GIT PATCH] " Inaky Perez-Gonzalez
2009-01-29 21:59     ` [PATCH] wimax: fix build issue when debugfs is disabled Inaky Perez-Gonzalez
2009-01-29 22:08       ` Randy Dunlap
2009-01-30  1:19         ` David Miller
2009-01-30  3:41           ` Inaky Perez-Gonzalez

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=20090130151251.GC27549@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=eduard.munteanu@linux360.ro \
    --cc=geert@linux-m68k.org \
    --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