From: Greg KH <gregkh@suse.de>
To: Alan Stern <stern@rowland.harvard.edu>,
Anoop P <anoop.pa@gmail.com>, Ralf Baechle <ralf@linux-mips.org>,
dbrownell@users.sourceforge.net, sarah.a.sharp@linux.intel.com,
andiry.xu@amd.com, agust@denx.de, ddaney@caviumnetworks.com,
gadiyar@ti.com, linux-mips@linux-mips.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] EHCI support for on-chip PMC MSP USB controller.
Date: Tue, 21 Dec 2010 09:59:42 -0800 [thread overview]
Message-ID: <20101221175942.GB8709@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1012211050470.31667-100000@netrider.rowland.org>
On Tue, Dec 21, 2010 at 11:00:02AM -0500, Alan Stern wrote:
> On Tue, 21 Dec 2010, Anoop P wrote:
>
> > From: Anoop P A <anoop.pa@gmail.com>
> >
> > This patch includes.
> >
> > 1. USB host driver for MSP71xx family SoC on-chip USB controller.
> > 2. Platform support for USB controller.
>
> It also contains changes to the core USB hub driver code. You should
> mention things like that in the patch description.
And that portion of the code should be split into a different patch to
make it easier to review.
thanks,
greg k-h
next prev parent reply other threads:[~2010-12-21 17:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 11:06 [PATCH] EHCI support for on-chip PMC MSP USB controller Anoop P
2010-12-21 16:00 ` Alan Stern
2010-12-21 17:59 ` Greg KH [this message]
2010-12-22 14:34 ` [PATCH V2 0/2] " Anoop P.A
2010-12-22 14:36 ` [PATCH V2 1/2] " Anoop P.A
2010-12-22 14:58 ` Anoop P A
2010-12-24 9:44 ` Shane McDonald
2011-01-27 11:28 ` [PATCH v3] EHCI bus glue " Anoop P.A
2011-02-04 19:56 ` Greg KH
2011-02-09 14:12 ` Anoop P A
2011-02-09 17:20 ` Greg KH
[not found] ` <4D52AE7E.8000907@parrot.com>
2011-02-09 15:44 ` Anoop P A
2011-02-15 10:43 ` [PATCH v4] " Anoop P.A
2010-12-22 14:36 ` [PATCH V2 2/2] MSP onchip root hub over current quirk Anoop P.A
2010-12-23 2:18 ` Alan Stern
2010-12-23 9:29 ` Anoop P A
2010-12-23 16:08 ` Alan Stern
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=20101221175942.GB8709@suse.de \
--to=gregkh@suse.de \
--cc=agust@denx.de \
--cc=andiry.xu@amd.com \
--cc=anoop.pa@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=ddaney@caviumnetworks.com \
--cc=gadiyar@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-usb@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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