linux-kernel - Re: [PATCH -next] kmemcheck: include module.h to prevent warnings

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] [day] [month] [year] [list]

Message-ID: <19f34abd0807261128k185110faxedd2a1d2a6078bfc@mail.gmail.com>
Date:	Sat, 26 Jul 2008 20:28:04 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Randy Dunlap" <randy.dunlap@...cle.com>,
	lkml <linux-kernel@...r.kernel.org>, vegardno@....uio.no,
	penberg@...helsinki.fi, akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH -next] kmemcheck: include module.h to prevent warnings

On Sat, Jul 26, 2008 at 5:43 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Randy Dunlap <randy.dunlap@...cle.com> wrote:
>
>> From: Randy Dunlap <randy.dunlap@...cle.com>
>>
>> kmemcheck/shadow.c needs to include <linux/module.h> to prevent
>> the following warnings:
>>
>> linux-next-20080724/arch/x86/mm/kmemcheck/shadow.c:64: warning : data definition has no type or storage class
>> linux-next-20080724/arch/x86/mm/kmemcheck/shadow.c:64: warning : type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL'
>> linux-next-20080724/arch/x86/mm/kmemcheck/shadow.c:64: warning : parameter names (without types) in function declaration
>
> applied to tip/kmemcheck - thanks Randy.

I am obviously also grateful for this patch. Thanks!


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/