From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yinbo Zhu <yinbo.zhu@nxp.com>
Cc: Felipe Balbi <balbi@ti.com>,
Mathias Nyman <mathias.nyman@intel.com>,
"open list:DESIGNWARE USB3 DRD IP DRIVER"
<linux-usb@vger.kernel.org>,
"open list:DESIGNWARE USB3 DRD IP DRIVER"
<linux-omap@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Xiaobo Xie <xiaobo.xie@nxp.com>,
Jerry Huang <jerry.huang@nxp.com>, Ran Wang <ran.wang_1@nxp.com>
Subject: Re: [PATCH v2] usb: host: Implement workaround for Erratum A-007463
Date: Mon, 11 Dec 2017 08:33:58 +0100 [thread overview]
Message-ID: <20171211073358.GA7712@kroah.com> (raw)
In-Reply-To: <VI1PR04MB1262B663F3B631E10E12D283E9370@VI1PR04MB1262.eurprd04.prod.outlook.com>
On Mon, Dec 11, 2017 at 02:26:02AM +0000, Yinbo Zhu wrote:
>
>
> -----Original Message-----
> From: Greg Kroah-Hartman [mailto:gregkh@linuxfoundation.org]
> Sent: Friday, December 08, 2017 6:18 PM
> To: Yinbo Zhu <yinbo.zhu@nxp.com>
> Cc: Felipe Balbi <balbi@ti.com>; Mathias Nyman <mathias.nyman@intel.com>; open list:DESIGNWARE USB3 DRD IP DRIVER <linux-usb@vger.kernel.org>; open list:DESIGNWARE USB3 DRD IP DRIVER <linux-omap@vger.kernel.org>; open list <linux-kernel@vger.kernel.org>; Xiaobo Xie <xiaobo.xie@nxp.com>; Jerry Huang <jerry.huang@nxp.com>; Ran Wang <ran.wang_1@nxp.com>
> Subject: Re: [PATCH v2] usb: host: Implement workaround for Erratum A-007463
>
> On Fri, Dec 08, 2017 at 05:49:40PM +0800, yinbo.zhu@nxp.com wrote:
> > From: "yinbo.zhu" <yinbo.zhu@nxp.com>
>
> >I need a "real name" here, I doubt you sign documents as:
> > "yinbo.zhu"
> >right? :)
>
> >Also, you sent 3 patches, yet no way to know what order to apply them in. Please fix that up by sending a >patch series, properly numbered.
>
> >thanks,
>
> >greg k-h
>
> Hi Greg Kroah-Hartman,
>
> "Yinbo.zhu" is my email address prefix,and it is automatically generated through the git command.
Then this means you have not correctly configured git, please fix that :)
> You can follow the order of patch A-007463 A-009611 A-009668 to apply it.
That's not how we number patches in the kernel, please do so in the
normal way. See the mailing lists for lots of examples. The kernel
documentation also describes the correct format for this.
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-11 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171208094942.46748-1-yinbo.zhu@nxp.com>
2017-12-08 10:17 ` [PATCH v2] usb: host: Implement workaround for Erratum A-007463 Greg Kroah-Hartman
2017-12-11 2:26 ` Yinbo Zhu
2017-12-11 7:33 ` Greg Kroah-Hartman [this message]
2017-12-11 8:08 ` Yinbo Zhu
[not found] ` <20171208094942.46748-2-yinbo.zhu@nxp.com>
2017-12-08 10:21 ` [PATCH v2] usb: host: Implement workaround for Erratum A-009611 Greg Kroah-Hartman
2017-12-08 10:44 ` Felipe Balbi
2017-12-11 3:15 ` Yinbo Zhu
2017-12-11 7:34 ` Greg Kroah-Hartman
2017-12-11 8:27 ` Yinbo Zhu
2017-12-11 8:51 ` Felipe Balbi
2017-12-12 7:09 ` Yinbo Zhu
2017-12-11 8:44 ` Yinbo Zhu
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=20171211073358.GA7712@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@ti.com \
--cc=jerry.huang@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=ran.wang_1@nxp.com \
--cc=xiaobo.xie@nxp.com \
--cc=yinbo.zhu@nxp.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