Date: Sun, 8 Nov 2009 11:58:49 +0000
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
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>,
       Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] slqb: A not quite so trivial warning
Message-ID: <20091108115849.24dc45a0@lxorguk.ukuu.org.uk>
In-Reply-To: <4AF6ADE1.60201@cs.helsinki.fi>
References: <20091106112942.14595.29799.stgit@localhost.localdomain>
	<4AF6ADE1.60201@cs.helsinki.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 720
Lines: 22

On Sun, 08 Nov 2009 13:39:13 +0200
Pekka Enberg <penberg@cs.helsinki.fi> wrote:

> Hi Alan,
> 
> 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__"?

I see it from -next on an x86-32 build
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/