[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <484FBA05.4010103@panasas.com>
Date: Wed, 11 Jun 2008 14:41:57 +0300
From: Boaz Harrosh <bharrosh@...asas.com>
To: Adrian Bunk <bunk@...nel.org>
CC: Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
David Woodhouse <dwmw2@...radead.org>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [2.6 patch] always enable FW_LOADER unless EMBEDDED=y
Adrian Bunk wrote:
> On Wed, Jun 11, 2008 at 12:20:05PM +0300, Boaz Harrosh wrote:
>> Adrian Bunk wrote:
>>> [1] and before anyone restarts the "kconfig is broken - select should
>>> follow dependencies" FUD: I've seen much talk and zero code for
>>> this, and in my opinion the problem is much more difficult than
>>> it appears at first sight
>> I had this crazy idea, Perhaps it would be easier to reverse the problem.
>> Introduce a kind of Lazy_Enable mode. Which means config is enabled but
>> gets it's use_count bumped up every time someone is dependent on it.
>> At the end, for optimization, any Lazy_Enable with zero count, is dropped.
>> Is that at all possible in current infrastructure?
>> (I admit I never looked at the source)
>
> Wouldn't your "Lazy_Enable" do the same as "select" already does?
>
No, I mean, for example, ISCSI_TCP will just "depends" on SCSI_ISCSI_ATTRS but
SCSI_ISCSI_ATTRS is Lazy_Enable. So a user can always choose ISCSI_TCP if he
wants to. At the end if there are no users for SCSI_ISCSI_ATTRS it is dropped.
Lazy_Enable is for these modules that say: "I have no purpose of my own
but only serve other needs"
Theoretically it looks like a simpler problem. (Pull vs Push)
>> Boaz
>
> cu
> Adrian
>
Just my $0.017
Boaz
--
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/
Powered by blists - more mailing lists