From: Kalle Valo <kvalo@kernel.org>
To: gregory.greenman@intel.com
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
"Johannes Berg" <johannes.berg@intel.com>,
"Íñigo Huguet" <ihuguet@redhat.com>
Subject: Re: [PATCH] wifi: iwlwifi: fw: skip PPAG for JF
Date: Wed, 14 Dec 2022 14:01:45 +0200 [thread overview]
Message-ID: <878rja19ee.fsf@kernel.org> (raw)
In-Reply-To: <20221213225723.2a43415d8990.I9ac210740a45b41f1b2e15274e1daf4284f2808a@changeid> (gregory greenman's message of "Tue, 13 Dec 2022 23:15:04 +0200")
gregory.greenman@intel.com writes:
> From: Johannes Berg <johannes.berg@intel.com>
>
> For JF RFs we don't support PPAG, but many firmware
> images lie about it. Always skip support for JF to
> avoid firmware errors when sending the command.
>
> Reported-and-tested-by: Íñigo Huguet <ihuguet@redhat.com>
> Link: https://lore.kernel.org/linux-wireless/CACT4oufQsqHGp6bah2c4+jPn2wG1oZqY=UKa_TmPx=F6Lxng8Q@mail.gmail.com
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> Signed-off-by: Gregory Greenman <gregory.greenman@intel.com>
> ---
>
> This is a fix for a firmware assert. It can wait until the next RC of v6.2.
Ok, I'll take this to wireless tree.
> Kalle - should I send a pull request for it? Thanks!
For patches to the wireless tree I prefer that I take them directly.
What I recommend is to assign the patch to me on patchwork and add
"v6.2" to the subject like this:
[PATCH v6.2] wifi: iwlwifi: fw: skip PPAG for JF
That way I'll then apply it automatically. But this for future patches,
I have now assigned this patch to me.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-12-14 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 21:15 [PATCH] wifi: iwlwifi: fw: skip PPAG for JF gregory.greenman
2022-12-14 12:01 ` Kalle Valo [this message]
2022-12-20 13:00 ` 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=878rja19ee.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=gregory.greenman@intel.com \
--cc=ihuguet@redhat.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).