From: Ingo Molnar <mingo@elte.hu>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH -next] x86: fix longstanding setup.c printk format warning
Date: Tue, 10 Jun 2008 12:24:52 +0200 [thread overview]
Message-ID: <20080610102452.GD19136@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0806051107200.702@shark.he.net>
* Randy.Dunlap <rdunlap@xenotime.net> wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Note: for -next only, not mainline.
>
> Fix setup.c printk format warning:
>
> linux-next-20080605/arch/x86/kernel/setup.c: In function 'setup_per_cpu_areas':
> linux-next-20080605/arch/x86/kernel/setup.c:173: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'ssize_t'
applied to tip/x86/numa - thanks Randy.
Ingo
prev parent reply other threads:[~2008-06-10 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 18:10 [PATCH -next] x86: fix longstanding setup.c printk format warning Randy.Dunlap
2008-06-10 10:24 ` Ingo Molnar [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=20080610102452.GD19136@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).