All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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_1@nxp.com
Subject: usb: dwc3: call set incr burst type func()
Date: Mon, 23 Jul 2018 07:16:05 +0200	[thread overview]
Message-ID: <20180723051605.GA13377@kroah.com> (raw)

On Mon, Jul 23, 2018 at 11:34:13AM +0800, Pengbo Mu wrote:
> Call dwc3_set_incr_burst_type() in dwc3_core_init().
> 

That says what you did, not why you are doing this.

Please fix up.

greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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_1@nxp.com
Subject: Re: [PATCH] usb: dwc3: call set incr burst type func()
Date: Mon, 23 Jul 2018 07:16:05 +0200	[thread overview]
Message-ID: <20180723051605.GA13377@kroah.com> (raw)
In-Reply-To: <1532316853-29184-1-git-send-email-pengbo.mu@nxp.com>

On Mon, Jul 23, 2018 at 11:34:13AM +0800, Pengbo Mu wrote:
> Call dwc3_set_incr_burst_type() in dwc3_core_init().
> 

That says what you did, not why you are doing this.

Please fix up.

greg k-h

             reply	other threads:[~2018-07-23  5:16 UTC|newest]

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

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=20180723051605.GA13377@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=balbi@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pengbo.mu@nxp.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.