linux-kernel - Re: [PATCH] slqb: A not quite so trivial warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091108115849.24dc45a0@lxorguk.ukuu.org.uk>
Date:	Sun, 8 Nov 2009 11:58:49 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Alan Cox <alan@...ux.intel.com>, mel@....ul.fi,
	linux-kernel@...r.kernel.org, Nick Piggin <npiggin@...e.de>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH] slqb: A not quite so trivial warning

On Sun, 08 Nov 2009 13:39:13 +0200
Pekka Enberg <penberg@...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@...ux.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/