linux-kernel - Re: [v4l-dvb-maintainer] [PATCH 35/36] Use menuconfig objects II

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: <Pine.LNX.4.61.0705031453360.18504@yvahk01.tjqt.qr>
Date:	Thu, 3 May 2007 14:54:56 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Mauro Carvalho Chehab <mchehab@...radead.org>
cc:	Trent Piepho <xyzzy@...akeasy.org>,
	v4l-dvb maintainer list <v4l-dvb-maintainer@...uxtv.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [v4l-dvb-maintainer] [PATCH 35/36] Use menuconfig objects II -
 DVB


On May 3 2007 09:37, Mauro Carvalho Chehab wrote:
>Trent is mentioning an out-of-tree building system to allow easier
>testing of V4L/DVB patches by end users and developers and during driver
>development time. The building system allows faster
>compilation/linkedition during driver development, by allowing you to
>use:
>	make menuconfig/qconfig/xconfig
>
>inside the tree, unselecting the drivers that you're not working.

Is that all? Because you can do

  make drivers/media/video/

today and it will only build that directory (or even
drivers/media/video/foo.o) to only do that one.

>The point rised by Trent is that, currently, this is not prepared to
>handle the "menuconfig" and "if/endif" tags.
>
>However, the v4l-dvb building system shouldn't stop improvements at the
>kernel building system. So, if there are any limits there, the proper
>solution is to fix the issues, instead of avoiding patches that could
>break it.


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