From: Tejun Heo <tj@kernel.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Alan Cox <alan@linux.intel.com>,
mel@csn.ul.fi, linux-kernel@vger.kernel.org,
Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH] slqb: A not quite so trivial warning
Date: Sun, 08 Nov 2009 21:04:22 +0900 [thread overview]
Message-ID: <4AF6B3C6.8080407@kernel.org> (raw)
In-Reply-To: <4AF6ADE1.60201@cs.helsinki.fi>
Hello,
Pekka Enberg wrote:
> Alan Cox wrote:
>> mm/slqb.c:2773: warning: initialization from incompatible pointer type
>>
>> Variable scope...
>>
>> Signed-off-by: Alan Cox <alan@linux.intel.com>
>
> I don't see this warning in my tree. Is this coming from linux-next? Did
> someone change DEFINE_PER_CPU not to prefix the variable name with
> "per_cpu__"?
Yeap, the prefix is dropped in the latest percpu tree. Patch already
pending.
http://patchwork.kernel.org/patch/56948/
Thanks.
--
tejun
next prev parent reply other threads:[~2009-11-08 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 11:29 [PATCH] slqb: A not quite so trivial warning Alan Cox
2009-11-08 11:39 ` Pekka Enberg
2009-11-08 11:58 ` Alan Cox
2009-11-08 12:04 ` Tejun Heo [this message]
2009-11-08 12:29 ` Pekka Enberg
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=4AF6B3C6.8080407@kernel.org \
--to=tj@kernel.org \
--cc=alan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.fi \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
/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