Hi,
On Wed, 16 May 2007, Al Viro wrote:
> On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
> >
> > stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
> > end up with unbuildable configs.
>
> BTW, this kind of situation happens often enough, so how about doing
> the
Hi,
On Wed, 16 May 2007, Al Viro wrote:
On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
end up with unbuildable configs.
BTW, this kind of situation happens often enough, so how about doing
the following:
Timur Tabi wrote:
> For example, if I want to add a new driver C that uses library B, I can
> just add this:
>
> C
> select B
>
> If I have to use "depends on", then I would have to change the Kconfig
> option for B like this:
>
> B
> depends on A || C
You mean, "B... serves A, C".
Timur Tabi wrote:
> Stefan Richter wrote:
>> "A... select B" is just a flavor of "A... depends on B",
...
> I think you mean "A... select B" is just a flavor of "B... depends on
> A".
No, A requires B's symbols.
--
Stefan Richter
-=-=-=== -=-= =---=
http://arcgraph.de/sr/
-
To unsubscribe
Stefan Richter wrote:
"A... select B" is just a flavor of "A... depends on B", with the
additional instruction to the Kconfig UIs: Don't hide A if you can
silently switch on B.
I think you mean "A... select B" is just a flavor of "B... depends on A". There is one
minor difference between
On 5/16/07, Al Viro <[EMAIL PROTECTED]> wrote:
On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
>
> stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
> end up with unbuildable configs.
BTW, this kind of situation happens often enough, so how about doing
the
On 5/16/07, Satyam Sharma <[EMAIL PROTECTED]> wrote:
On 5/16/07, Al Viro <[EMAIL PROTECTED]> wrote:
> On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
> >
> > stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
> > end up with unbuildable configs.
>
> BTW, this kind of
Al Viro wrote:
>> stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
>> end up with unbuildable configs.
>
> BTW, this kind of situation happens often enough, so how about doing
> the following: teach kconfig that if FOO selects BAR and BAR depends
> on , we should act as if
On Wed, May 16, 2007 at 04:33:35AM +0100, Al Viro wrote:
> On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
> >
> > stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
> > end up with unbuildable configs.
>
> BTW, this kind of situation happens often enough, so how
On Wed, May 16, 2007 at 04:33:35AM +0100, Al Viro wrote:
On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
end up with unbuildable configs.
BTW, this kind of situation happens often enough, so how about doing
Al Viro wrote:
stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
end up with unbuildable configs.
BTW, this kind of situation happens often enough, so how about doing
the following: teach kconfig that if FOO selects BAR and BAR depends
on expr, we should act as if FOO
On 5/16/07, Satyam Sharma [EMAIL PROTECTED] wrote:
On 5/16/07, Al Viro [EMAIL PROTECTED] wrote:
On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
end up with unbuildable configs.
BTW, this kind of situation
On 5/16/07, Al Viro [EMAIL PROTECTED] wrote:
On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
end up with unbuildable configs.
BTW, this kind of situation happens often enough, so how about doing
the following:
Stefan Richter wrote:
A... select B is just a flavor of A... depends on B, with the
additional instruction to the Kconfig UIs: Don't hide A if you can
silently switch on B.
I think you mean A... select B is just a flavor of B... depends on A. There is one
minor difference between the two.
Timur Tabi wrote:
Stefan Richter wrote:
A... select B is just a flavor of A... depends on B,
...
I think you mean A... select B is just a flavor of B... depends on
A.
No, A requires B's symbols.
--
Stefan Richter
-=-=-=== -=-= =---=
http://arcgraph.de/sr/
-
To unsubscribe from this list:
Timur Tabi wrote:
For example, if I want to add a new driver C that uses library B, I can
just add this:
C
select B
If I have to use depends on, then I would have to change the Kconfig
option for B like this:
B
depends on A || C
You mean, B... serves A, C.
However, it
On Wed, 16 May 2007, Al Viro wrote:
>
> BTW, this kind of situation happens often enough, so how about doing
> the following: teach kconfig that if FOO selects BAR and BAR depends
> on , we should act as if FOO had explicit depends on .
Sounds sane. I wonder if there are any non-obvious
On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
>
> stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
> end up with unbuildable configs.
BTW, this kind of situation happens often enough, so how about doing
the following: teach kconfig that if FOO selects BAR and BAR
On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
end up with unbuildable configs.
BTW, this kind of situation happens often enough, so how about doing
the following: teach kconfig that if FOO selects BAR and BAR
On Wed, 16 May 2007, Al Viro wrote:
BTW, this kind of situation happens often enough, so how about doing
the following: teach kconfig that if FOO selects BAR and BAR depends
on expr, we should act as if FOO had explicit depends on expr.
Sounds sane. I wonder if there are any non-obvious
20 matches
Mail list logo
