linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Alessio Bonfiglio <alessio.bonfiglio@mail.polimi.it>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes.berg@intel.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Luca Coelho <luciano.coelho@intel.com>,
	Intel Linux Wireless <linuxwifi@intel.com>
Subject: Re: [PATCH v2] iwlwifi: Make some Killer Wireless-AC 1550 cards work again
Date: Tue, 14 Jul 2020 14:24:08 +0300	[thread overview]
Message-ID: <CANUX_P3jbE__37Osw2PEZzrwjkxdZXUn-Kb+AmMRUyAAjp+8cQ@mail.gmail.com> (raw)
In-Reply-To: <877dv6cthg.fsf@tynnyri.adurom.net>

> Alessio Bonfiglio <alessio.bonfiglio@mail.polimi.it> writes:
>
> > Fix the regression introduced by commit c8685937d07f ("iwlwifi: move
> > pu devices to new table") by adding the ids and the configurations of
> > two missing Killer 1550 cards in order to configure and let them work
> > correctly again (following the new table convention).
> > Resolve bug 208141 ("Wireless ac 9560 not working kernel 5.7.2",
> > https://bugzilla.kernel.org/show_bug.cgi?id=208141).
> >
> > Fixes: c8685937d07f ("iwlwifi: move pu devices to new table")
> > Signed-off-by: Alessio Bonfiglio <alessio.bonfiglio@mail.polimi.it>
>
> Luca, should I take this to v5.8?

Luca is OOO, but I guess you should, yes.

Thanks.

  reply	other threads:[~2020-07-14 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 15:05 [PATCH] iwlwifi: Make some Killer Wireless-AC 1550 cards working again Alessio Bonfiglio
2020-07-14  8:52 ` Kalle Valo
2020-07-14  9:19   ` [PATCH v2] iwlwifi: Make some Killer Wireless-AC 1550 cards work again Alessio Bonfiglio
2020-07-14  9:54     ` Kalle Valo
2020-07-14 11:24       ` Emmanuel Grumbach [this message]
2020-07-20 16:39     ` Kalle Valo

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=CANUX_P3jbE__37Osw2PEZzrwjkxdZXUn-Kb+AmMRUyAAjp+8cQ@mail.gmail.com \
    --to=egrumbach@gmail.com \
    --cc=alessio.bonfiglio@mail.polimi.it \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@intel.com \
    --cc=luciano.coelho@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).