linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pengbo Mu <pengbo.mu@nxp.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Felipe Balbi <balbi@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Ran Wang <ran.wang_1@nxp.com>
Subject: RE: [PATCH] usb: dwc3: call set incr burst type func()
Date: Mon, 23 Jul 2018 07:48:54 +0000	[thread overview]
Message-ID: <AM0PR0402MB3747D90C3CCC931128EEB108F4560@AM0PR0402MB3747.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20180723070027.GB20056@kroah.com>

I have realized this will cause confusion.
Will remake it !

Thanks,
Pengbo Mu
-----Original Message-----
From: Greg Kroah-Hartman [mailto:gregkh@linuxfoundation.org] 
Sent: 2018年7月23日 15:00
To: Pengbo Mu <pengbo.mu@nxp.com>
Cc: Felipe Balbi <balbi@kernel.org>; linux-kernel@vger.kernel.org; linux-usb@vger.kernel.org; Ran Wang <ran.wang_1@nxp.com>
Subject: Re: [PATCH] usb: dwc3: call set incr burst type func()

On Mon, Jul 23, 2018 at 02:40:57PM +0800, Pengbo Mu wrote:
> Calling dwc3_set_incr_burst_type() in dwc3_core_init().
> This function enabled the undefined length INCR burst type and set 
> INCRx. Different platform may has the different burst size type. In 
> order to get best performance, we need to tune the burst size to one 
> special value, instead of the default value.
> 
> Signed-off-by: Pengbo Mu <pengbo.mu@nxp.com>
> ---
> Changes in v1:
>  - add the calling of dwc3_set_incr_burst_type.

This isn't the changelog :(  You also didn't version the patch in the [PATCH] area :(

Please put this as part of the other series properly.

thanks,

greg k-h

  reply	other threads:[~2018-07-23  7:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23  6:40 [PATCH] usb: dwc3: call set incr burst type func() Pengbo Mu
2018-07-23  7:00 ` Greg Kroah-Hartman
2018-07-23  7:48   ` Pengbo Mu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-23  3:34 Pengbo Mu
2018-07-23  5:16 ` Greg Kroah-Hartman
2018-07-23  6:37   ` Pengbo Mu
2018-07-23  6:59     ` Greg Kroah-Hartman
2018-07-23  7:05 ` kbuild test robot
2018-07-23  9:29   ` Pengbo Mu
2018-07-23 10:03     ` Felipe Balbi
2018-07-23 10:35       ` Pengbo Mu
2018-07-23  7:10 ` kbuild test robot

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=AM0PR0402MB3747D90C3CCC931128EEB108F4560@AM0PR0402MB3747.eurprd04.prod.outlook.com \
    --to=pengbo.mu@nxp.com \
    --cc=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ran.wang_1@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;
as well as URLs for NNTP newsgroup(s).