From: Greg KH <gregkh@suse.de>
To: Fushen Chen <fchen@apm.com>
Cc: linuxppc-dev@ozlabs.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 0/2 v1.04] Add support for DWC OTG driver.
Date: Wed, 28 Jul 2010 20:05:59 -0700 [thread overview]
Message-ID: <20100729030559.GA16667@suse.de> (raw)
In-Reply-To: <12803633233020-git-send-email-fchen@apm.com>
On Wed, Jul 28, 2010 at 05:28:41PM -0700, Fushen Chen wrote:
> [PATCH 1/2 v1.04]
> 1. License information is under clarification.
What do you mean by this? I fail to see a change here, why just repost
the same code again?
What is being done to resolve the issues I outlined previously?
greg k-h
next prev parent reply other threads:[~2010-07-29 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 0:28 [PATCH 0/2 v1.04] Add support for DWC OTG driver Fushen Chen
2010-07-29 0:28 ` [PATCH 1/2 v1.04] Add support for DWC OTG HCD function Fushen Chen
2010-07-29 0:28 ` [PATCH 2/2 v1.04] Add support for DWC OTG PCD function Fushen Chen
2010-07-29 3:05 ` Greg KH [this message]
2010-07-29 16:26 ` [PATCH 0/2 v1.04] Add support for DWC OTG driver Fushen Chen
2010-07-29 17:22 ` Greg KH
2010-07-30 0:42 ` David Daney
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=20100729030559.GA16667@suse.de \
--to=gregkh@suse.de \
--cc=fchen@apm.com \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).