From: patchwork-bot+netdevbpf@kernel.org
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
johannes.berg@intel.com, xry111@xry111.site,
pinkflames.linux@gmail.com, jeff.chua.linux@gmail.com,
rui.zhang@intel.com
Subject: Re: [PATCH net] wifi: iwlwifi: remove 'use_tfh' config to fix crash
Date: Wed, 12 Jul 2023 03:30:21 +0000 [thread overview]
Message-ID: <168913262132.27250.2841776474706788914.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230710145038.84186-2-johannes@sipsolutions.net>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 10 Jul 2023 16:50:39 +0200 you wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> This is equivalent to 'gen2', and it was always confusing to have
> two identical config entries. The split config patch actually had
> been originally developed after removing 'use_tfh" and didn't add
> the use_tfh in the new configs as they'd later been copied to the
> new files. Thus the easiest way to fix the init crash here now is
> to just remove use_tfh (which is erroneously unset in most of the
> configs now) and use 'gen2' in the code instead.
>
> [...]
Here is the summary with links:
- [net] wifi: iwlwifi: remove 'use_tfh' config to fix crash
https://git.kernel.org/netdev/net/c/12a89f017709
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-07-12 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 14:50 [PATCH net] wifi: iwlwifi: remove 'use_tfh' config to fix crash Johannes Berg
2023-07-12 3:30 ` patchwork-bot+netdevbpf [this message]
2023-07-12 15:33 ` Rudi Heitbaum
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=168913262132.27250.2841776474706788914.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=jeff.chua.linux@gmail.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pinkflames.linux@gmail.com \
--cc=rui.zhang@intel.com \
--cc=xry111@xry111.site \
/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