From: Luciano Coelho <luciano.coelho@intel.com>
To: Kalle Valo <kvalo@codeaurora.org>,
"Jan Alexander Steffens (heftig)" <jan.steffens@gmail.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>,
"David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: pcie: restore support for Killer Qu C0 NICs
Date: Wed, 04 Mar 2020 09:10:24 +0200 [thread overview]
Message-ID: <4e26c715b81fdea7d10e19ca46ffd2645cbe78f9.camel@intel.com> (raw)
In-Reply-To: <20200303152925.6BCA8C4479F@smtp.codeaurora.org>
On Tue, 2020-03-03 at 15:29 +0000, Kalle Valo wrote:
> "Jan Alexander Steffens (heftig)" <jan.steffens@gmail.com> wrote:
>
> > Commit 809805a820c6 ("iwlwifi: pcie: move some cfg mangling from
> > trans_pcie_alloc to probe") refactored the cfg mangling. Unfortunately,
> > in this process the lines which picked the right cfg for Killer Qu C0
> > NICs after C0 detection were lost. These lines were added by commit
> > b9500577d361 ("iwlwifi: pcie: handle switching killer Qu B0 NICs to
> > C0").
> >
> > I suspect this is more of the "merge damage" which commit 7cded5658329
> > ("iwlwifi: pcie: fix merge damage on making QnJ exclusive") talks about.
> >
> > Restore the missing lines so the driver loads the right firmware for
> > these NICs.
> >
> > Fixes: 809805a820c6 ("iwlwifi: pcie: move some cfg mangling from trans_pcie_alloc to probe")
> > Signed-off-by: Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>
>
> As Luca said, this fails to apply to wireless-drivers. Please rebase and
> resend as v2.
Hmmm, sorry, I confused things a bit. I missed the fact that wireless-
drivers is already at v5.6.
This patch is not needed in v5.6-rc* because another patch has done a
similar change. There was some refactoring in this area, so the patch
that is in v5.6 doesn't apply in v5.5, so Jan's patch has to be sent to
stable v5.5 and not be applied in wireless-drivers.
Jan, if you want this to be fixed in v5.5, can you please send it to
stable@vger.kernel.org with an explanation of why it has to be there
even though it's not in the mainline? Or just send it and CC me, so
I'll reply with an explanation of the issue.
--
Cheers,
Luca.
prev parent reply other threads:[~2020-03-04 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 5:16 [PATCH] iwlwifi: pcie: restore support for Killer Qu C0 NICs Jan Alexander Steffens (heftig)
2020-02-21 12:11 ` Leho Kraav
2020-03-03 5:40 ` Kalle Valo
2020-03-03 8:17 ` Luca Coelho
2020-03-03 15:29 ` Kalle Valo
[not found] ` <20200303152925.6BCA8C4479F@smtp.codeaurora.org>
2020-03-04 7:10 ` Luciano Coelho [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=4e26c715b81fdea7d10e19ca46ffd2645cbe78f9.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=davem@davemloft.net \
--cc=emmanuel.grumbach@intel.com \
--cc=jan.steffens@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).