All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: luciano.coelho@intel.com, johannes.berg@intel.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] iwlwifi: pcie: handle switching killer Qu B0 NICs to C0" failed to apply to 5.2-stable tree
Date: Tue, 3 Sep 2019 16:53:21 -0400	[thread overview]
Message-ID: <20190903205321.GP5281@sasha-vm> (raw)
In-Reply-To: <15675370949856@kroah.com>

On Tue, Sep 03, 2019 at 08:58:14PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.2-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>.

There are quite a few dependencies here - it looks like a few other
stable tagged commits didn't make it to 5.2 and this one depends on
them. I've fixed it up by taking:

d151b0a2efa12 ("iwlwifi: add new cards for 22000 and fix struct name")
a976bfb44bdbc ("iwlwifi: add new cards for 22000 and change wrong structs")
ffcb60a54f245 ("iwlwifi: add new cards for 9000 and 20000 series")
658521fc1bf14 ("iwlwifi: change 0x02F0 fw from qu to quz")
a7d544d631200 ("iwlwifi: pcie: add support for qu c-step devices")
17e40e6979aaf ("iwlwifi: pcie: don't switch FW to qnj when ax201 is detected")
b9500577d3615 ("iwlwifi: pcie: handle switching killer Qu B0 NICs to C0")

--
Thanks,
Sasha

  reply	other threads:[~2019-09-03 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 18:58 FAILED: patch "[PATCH] iwlwifi: pcie: handle switching killer Qu B0 NICs to C0" failed to apply to 5.2-stable tree gregkh
2019-09-03 20:53 ` Sasha Levin [this message]
2019-09-04  8:16   ` Luciano Coelho

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=20190903205321.GP5281@sasha-vm \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes.berg@intel.com \
    --cc=luciano.coelho@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 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.