From: Kalle Valo <kvalo@kernel.org>
To: Yi Kuo <yi@yikuo.dev>
Cc: gregory.greenman@intel.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: pcie: add device id 51F1 for killer 1675
Date: Fri, 14 Apr 2023 16:45:20 +0300 [thread overview]
Message-ID: <87bkjqshlb.fsf@kernel.org> (raw)
In-Reply-To: <20230410222221.27587-1-yi@yikuo.dev> (Yi Kuo's message of "Tue, 11 Apr 2023 06:22:21 +0800")
Yi Kuo <yi@yikuo.dev> writes:
> I have a Killer AX1675i card with device id 51f1,
> showing "No config found for PCI dev 51f1/1672" in dmesg.
>
> Adding the new device id 51F1 for 1675i fixes the issue.
> Also adding it for 1675s.
>
> Signed-off-by: Yi Kuo <yi@yikuo.dev>
> ---
> drivers/net/wireless/intel/iwlwifi/pcie/drv.c | 2 ++
> 1 file changed, 2 insertions(+)
"wifi:" missing from title.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-04-14 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 22:22 [PATCH] iwlwifi: pcie: add device id 51F1 for killer 1675 Yi Kuo
2023-04-14 13:45 ` Kalle Valo [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=87bkjqshlb.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=gregory.greenman@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=yi@yikuo.dev \
/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).