Re: linux-next: usb tree build failure

From: Dmitry <dbaryshkov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>, linux-next@vger.kernel.org
Subject: Re: linux-next: usb tree build failure
Date: Fri, 17 Oct 2008 04:41:50 +0400	[thread overview]
Message-ID: <bc64b4640810161741g5329d8c1od6910f05352370b8@mail.gmail.com> (raw)
In-Reply-To: <20081017112610.83a67160.sfr@canb.auug.org.au>

2008/10/17 Stephen Rothwell <sfr@canb.auug.org.au>:
> Hi Dmitry,
>
> On Fri, 17 Oct 2008 01:36:13 +0400 Dmitry Baryshkov <dbaryshkov@gmail.com> wrote:
>>
>> After few tries I can come with pretty simple but pretty strange solution:
>>
>> >From 1c6dd41e074c5f526fc29b00a2bf265497d2819d Mon Sep 17 00:00:00 2001
>> From: Dmitry Baryshkov <dbaryshkov@gmail.com>
>> Date: Fri, 17 Oct 2008 01:30:15 +0400
>> Subject: [PATCH] USB: unbreak recursive dependancy
>>
>> After addition of TMIO usb driver Kconfig sees the recursive dependency
>> Break it by rephrasing ARCH_PNX4008 OHCI deps.
>
> I will add this to today's linux-next, thanks.

Thank you. However I suggest to take this as a precaution. As kernel
grows, various interdeps
also grow. I fear that soon we will have to rewrite Kconfig
depencencies to take care
upon impossible combinations of symbols (the chain that raised this
topic is impossible,
as I said before).

-- 
With best wishes
Dmitry