From: Boaz Harrosh <bharrosh@panasas.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6 patch] always enable FW_LOADER unless EMBEDDED=y
Date: Wed, 11 Jun 2008 14:41:57 +0300 [thread overview]
Message-ID: <484FBA05.4010103@panasas.com> (raw)
In-Reply-To: <20080611095921.GN11685@cs181133002.pp.htv.fi>
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
next prev parent reply other threads:[~2008-06-11 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 16:04 [2.6 patch] always enable FW_LOADER unless EMBEDDED=y Adrian Bunk
2008-06-10 16:24 ` Greg KH
2008-06-10 18:12 ` Adrian Bunk
2008-06-10 21:28 ` Greg KH
2008-06-11 8:23 ` Adrian Bunk
2008-06-11 9:20 ` Boaz Harrosh
2008-06-11 9:59 ` Adrian Bunk
2008-06-11 11:41 ` Boaz Harrosh [this message]
2008-06-11 18:20 ` Greg KH
2008-06-11 19:38 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=484FBA05.4010103@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.