linux-kernel - Re: [PATCH] BLOCK: Make it possible to disable the block layer

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: <1156426859.3012.36.camel@pmac.infradead.org>
Date:	Thu, 24 Aug 2006 14:40:59 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	David Howells <dhowells@...hat.com>
Cc:	Jens Axboe <axboe@...e.de>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer

On Thu, 2006-08-24 at 14:34 +0100, David Howells wrote:
> Ah, but...  The core kernel makes use of the certain header files, even when
> their actual intended target is compiled as a module.  If I just use
> "CONFIG_foo" only, then the module won't compile as a module. 

So don't put it in the header file itself. Just do 

	#ifdef CONFIG_foo
	#include <linux/foo.h>
	#endif

Better still, avoid the need for the external code to poke at fs-private
header files at all.

-- 
dwmw2

-
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/