From: Tejun Heo <tj@kernel.org>
To: Ingo Molnar <mingo@elte.hu>,
x86@kernel.org, Johannes Weiner <hannes@cmpxchg.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rusty Russell <rusty@rustcorp.com.au>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH tj-percpu 1/3] percpu: kill compile warning in pcpu_populate_chunk()
Date: Sun, 01 Mar 2009 16:13:00 +0900 [thread overview]
Message-ID: <49AA357C.3070006@kernel.org> (raw)
Impact: remove compile warning
Mark local variable map_end in pcpu_populate_chunk() with
uninitialized_var(). The variable is always used in tandem with
map_start and guaranteed to be initialized before use but gcc doesn't
understand that.
Signed-off-by: Tejun Heo <tj@kernel.org>
Reported-by: Ingo Molnar <mingo@elte.hu>
---
This the first of three misc fix patches for #tj-percpu. Patches are
also available in the tj-percpu git tree.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git tj-percpu
Thanks.
mm/percpu.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/mm/percpu.c b/mm/percpu.c
index 5954e7a..3d0f545 100644
--- a/mm/percpu.c
+++ b/mm/percpu.c
@@ -639,7 +639,7 @@ static int pcpu_populate_chunk(struct pcpu_chunk *chunk, int off, int size)
int page_start = PFN_DOWN(off);
int page_end = PFN_UP(off + size);
int map_start = -1;
- int map_end;
+ int uninitialized_var(map_end);
unsigned int cpu;
int i;
--
1.6.0.2
next reply other threads:[~2009-03-01 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 7:13 Tejun Heo [this message]
2009-03-01 7:13 ` [PATCH tj-percpu 2/3] alpha: fix typo in recent early vmalloc change Tejun Heo
2009-03-01 7:14 ` [PATCH tj-percpu 3/3] bootmem, x86: further fixes for arch-specific bootmem wrapping Tejun Heo
2009-03-02 9:07 ` [PATCH tj-percpu 1/3] percpu: kill compile warning in pcpu_populate_chunk() Ingo Molnar
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=49AA357C.3070006@kernel.org \
--to=tj@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.