Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: henryl@nvidia.com, mathias.nyman@linux.intel.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] usb: xhci: only set D3hot for pci device" failed to apply to 4.9-stable tree
Date: Sun, 15 Dec 2019 12:39:00 -0500	[thread overview]
Message-ID: <20191215173859.GF18043@sasha-vm> (raw)
In-Reply-To: <157640185110204@kroah.com>

On Sun, Dec 15, 2019 at 10:24:11AM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From f2c710f7dca8457e88b4ac9de2060f011254f9dd Mon Sep 17 00:00:00 2001
>From: Henry Lin <henryl@nvidia.com>
>Date: Wed, 11 Dec 2019 16:20:04 +0200
>Subject: [PATCH] usb: xhci: only set D3hot for pci device
>
>Xhci driver cannot call pci_set_power_state() on non-pci xhci host
>controllers. For example, NVIDIA Tegra XHCI host controller which acts
>as platform device with XHCI_SPURIOUS_WAKEUP quirk set in some platform
>hits this issue during shutdown.
>
>Cc: <stable@vger.kernel.org>
>Fixes: 638298dc66ea ("xhci: Fix spurious wakeups after S5 on Haswell")
>Signed-off-by: Henry Lin <henryl@nvidia.com>
>Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
>Link: https://lore.kernel.org/r/20191211142007.8847-4-mathias.nyman@linux.intel.com
>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Fixed up and queued for 4.9 and 4.4.

-- 
Thanks,
Sasha

      reply	other threads:[~2019-12-15 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15  9:24 FAILED: patch "[PATCH] usb: xhci: only set D3hot for pci device" failed to apply to 4.9-stable tree gregkh
2019-12-15 17:39 ` Sasha Levin [this message]

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=20191215173859.GF18043@sasha-vm \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=henryl@nvidia.com \
    --cc=mathias.nyman@linux.intel.com \
    --cc=stable@vger.kernel.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