From: Greg KH <greg@kroah.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.10] ehci "hc died" on startup (chip bug workaround)
Date: Fri, 7 Jan 2005 10:29:28 -0800 [thread overview]
Message-ID: <20050107182928.GA29599@kroah.com> (raw)
In-Reply-To: <200501071005.43520.david-b@pacbell.net>
On Fri, Jan 07, 2005 at 10:05:43AM -0800, David Brownell wrote:
> On Friday 07 January 2005 9:43 am, Greg KH wrote:
> > On Wed, Jan 05, 2005 at 02:35:42PM -0800, David Brownell wrote:
> > > We seem to have tracked some annoying board-coupled EHCI startup
> > > problems to a chip bug, with a simple workaround. Please merge.
> >
> > Hm, I get a reject from this:
> > ...
> >
> > What kernel tree is it against?
>
> Probably my gadget-2.6 tree; here's one that applies against
> current 2.5 BK or your USB integration tree. Sorry!
Ah, much better, that worked. Thanks, applied.
greg k-h
prev parent reply other threads:[~2005-01-07 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 22:35 [patch 2.6.10] ehci "hc died" on startup (chip bug workaround) David Brownell
2005-01-07 17:43 ` Greg KH
2005-01-07 18:05 ` David Brownell
2005-01-07 18:29 ` Greg KH [this message]
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=20050107182928.GA29599@kroah.com \
--to=greg@kroah.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox