linux-kernel - Re: [GIT]: Networking

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: <20090105.220742.176919041.davem@davemloft.net>
Date:	Mon, 05 Jan 2009 22:07:42 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	sam@...nborg.org
Cc:	jaswinderlinux@...il.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, dwmw2@...radead.org
Subject: Re: [GIT]: Networking

From: Sam Ravnborg <sam@...nborg.org>
Date: Tue, 6 Jan 2009 06:51:44 +0100

> We should avoid a central file and push this information
> out to the Kconfig files that are at the driver site.
> 
> Then we can postprocess autoconf.h to get the filenames etc.

I'll take this opportunity to once again promote my idea wherein build
information (and perhaps other bits like firmware info) for a driver
is encoded into the source of the driver itself, and the build system
just extracts that stuff into Makefiles and whatnot at build time. :-)

Couldn't resist.
--
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/