From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dmitry Baryshkov <dbaryshkov@gmail•com>
Cc: Greg KH <greg@kroah•com>, linux-next@vger•kernel.org
Subject: Re: linux-next: usb tree build failure
Date: Fri, 17 Oct 2008 11:26:10 +1100 [thread overview]
Message-ID: <20081017112610.83a67160.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20081016213613.GB11876@doriath.ww600.siemens.net>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
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.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-17 0:26 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 3:59 linux-next: usb tree build failure Stephen Rothwell
2008-10-14 8:24 ` Dmitry
2008-10-14 15:42 ` Dmitry
2008-10-16 16:05 ` Greg KH
2008-10-16 17:27 ` Dmitry Baryshkov
2008-10-16 21:36 ` Dmitry Baryshkov
2008-10-17 0:26 ` Stephen Rothwell [this message]
2008-10-17 0:41 ` Dmitry
2008-10-20 18:45 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-02-02 6:10 Stephen Rothwell
2010-02-02 13:53 ` Greg KH
2010-02-02 22:33 ` Stephen Rothwell
2009-08-19 8:34 Stephen Rothwell
2009-08-19 13:52 ` Greg KH
2009-08-19 23:45 ` Greg KH
2009-08-19 23:58 ` Stephen Rothwell
2009-04-29 7:17 Stephen Rothwell
2009-04-29 14:15 ` Greg KH
2009-04-29 15:00 ` Stephen Rothwell
2009-04-29 15:16 ` Greg KH
2009-04-29 15:18 ` Randy Dunlap
2009-04-29 15:37 ` Greg KH
2009-04-29 15:44 ` Randy Dunlap
2009-04-29 17:44 ` Greg KH
2009-04-29 17:53 ` Randy Dunlap
2009-04-30 16:13 ` Greg KH
2009-04-30 16:27 ` Randy Dunlap
2008-12-22 0:33 Stephen Rothwell
2008-12-22 1:31 ` Greg KH
2008-12-22 2:42 ` Stephen Rothwell
2008-12-22 6:45 ` Sam Ravnborg
2008-12-22 17:26 ` Inaky Perez-Gonzalez
2008-12-22 17:53 ` Sam Ravnborg
2008-12-22 23:37 ` Inaky Perez-Gonzalez
2008-12-23 4:31 ` Greg KH
2008-12-23 4:30 ` Greg KH
2008-12-23 4:31 ` Greg KH
2008-12-23 10:26 ` Inaky Perez-Gonzalez
2008-12-23 17:17 ` Greg KH
2008-12-24 1:07 ` Inaky Perez-Gonzalez
2009-01-05 4:34 ` Greg KH
2009-01-05 5:55 ` Stephen Rothwell
2008-12-29 3:55 ` Stephen Rothwell
2009-01-02 7:27 ` Greg KH
2009-01-03 4:33 ` Stephen Rothwell
2008-11-03 0:36 Stephen Rothwell
2008-11-05 4:47 ` Greg KH
2008-11-05 18:19 ` Mauro Carvalho Chehab
2008-10-14 4:08 Stephen Rothwell
2008-10-14 5:51 ` Alexey Klimov
2008-10-14 17:41 ` Alexey Klimov
2008-10-14 17:26 ` Mauro Carvalho Chehab
2008-08-13 6:37 Stephen Rothwell
2008-08-13 7:33 ` Stephen Rothwell
2008-08-13 14:23 ` Stephen Rothwell
2008-08-14 6:28 ` Stephen Rothwell
2008-08-14 6:54 ` Stephen Rothwell
2008-08-14 12:25 ` Greg KH
2008-08-15 0:16 ` Stephen Rothwell
2008-07-18 1:31 Stephen Rothwell
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=20081017112610.83a67160.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dbaryshkov@gmail$(echo .)com \
--cc=greg@kroah$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox