From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net, linux-mips@linux-mips.org,
thomas.dahlmann@amd.com
Subject: Re: EHCI support for the AU1200
Date: Mon, 23 Jan 2006 08:05:17 -0700 [thread overview]
Message-ID: <20060123150517.GD4371@cosmic.amd.com> (raw)
In-Reply-To: <200601201736.47548.david-b@pacbell.net>
On 20/01/06 17:36 -0800, David Brownell wrote:
> On Friday 13 January 2006 10:30 am, Jordan Crouse wrote:
> > ALCHEMY: ?Add EHCI support for AU1200
>
> Unfortunately it doesn't apply to my current tree, and I see that
> you were reverting some of the updates in current kernel GIT ...
Doh - reverting changes is wicked bad - I must have screwed up the merge
somewhere along the line.
> Please let me know if the updated version I'm posting does not
> behave for you.
Will do.
Jordan
--
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>
prev parent reply other threads:[~2006-01-23 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 18:30 [PATCH] EHCI support for the AU1200 Jordan Crouse
2006-01-21 1:36 ` [linux-usb-devel] " David Brownell
2006-01-23 15:05 ` Jordan Crouse [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=20060123150517.GD4371@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=david-b@pacbell.net \
--cc=linux-mips@linux-mips.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=thomas.dahlmann@amd.com \
/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