linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: linux-usb@vger.kernel.org, Chunfeng Yun <chunfeng.yun@mediatek.com>
Subject: [01/10] usb: xhci-mtk: resume USB3 roothub first
Date: Thu, 20 Sep 2018 12:36:51 +0200	[thread overview]
Message-ID: <20180920103651.GC14252@kroah.com> (raw)

On Mon, Sep 17, 2018 at 10:35:46AM +0300, Mathias Nyman wrote:
> On 14.09.2018 16:27, Greg KH wrote:
> > On Thu, Sep 13, 2018 at 03:23:54PM +0300, Mathias Nyman wrote:
> > > From: Chunfeng Yun <chunfeng.yun@mediatek.com>
> > > 
> > > Give USB3 devices a better chance to enumerate at USB3 speeds if
> > > they are connected to a suspended host.
> > > Porting from "671ffdff5b13 xhci: resume USB 3 roothub first"
> > > 
> > > Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> > > Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
> > > ---
> > >   drivers/usb/host/xhci-mtk.c | 4 ++--
> > >   1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > Isn't this a bugfix for 4.19-final?  And maybe for stable?
> > 
> 
> This was part of a 6 patch series that mostly contained mediatek
> bandwidth scheduling improvements.
> 
> But I agree, this first one could go to 4.19 with stable flag.

Ok, can you redo this whole series, and the 4.19-final series, so we get
these all straightened out as to which patch goes where, and resend?

I've dropped all of your pending patches from my queue now.

thanks,

greg k-h

             reply	other threads:[~2018-09-20 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 10:36 Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-17  7:35 [01/10] usb: xhci-mtk: resume USB3 roothub first Mathias Nyman
2018-09-14 13:27 Greg Kroah-Hartman
2018-09-13 12:23 Mathias Nyman

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=20180920103651.GC14252@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chunfeng.yun@mediatek.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.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).