From: Greg KH <gregkh@linuxfoundation.org>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: stable@vger.kernel.org, Jeff Johnson <jjohnson@kernel.org>,
linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org, Gregoire <gregoire.s93@live.fr>,
Sebastian Reichel <sre@kernel.org>,
Baochen Qiang <quic_bqiang@quicinc.com>,
Johan Hovold <johan@kernel.org>
Subject: Re: Stable Request: wifi: ath12k: install pairwise key first
Date: Tue, 12 Aug 2025 18:27:00 +0200 [thread overview]
Message-ID: <2025081240-trustless-secret-1354@gregkh> (raw)
In-Reply-To: <053a7887-c08d-4272-8ada-cf4a008894f9@oss.qualcomm.com>
On Tue, Aug 12, 2025 at 08:58:52AM -0700, Jeff Johnson wrote:
> Stable team,
>
> Per https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> Option 2 (since the patch was merged before being identified for -stable)
> Please consider the following for -stable
>
> subject of the patch:
> wifi: ath12k: install pairwise key first
>
> commit ID:
> 66e865f9dc78d00e6d1c8c6624cb0c9004e5aafb
>
> why you think it should be applied:
> This issue impacts all products that use iwd (instead of wpa_supplicant) for
> WLAN driver management
>
> what kernel versions you wish it to be applied to:
> All LTS kernels from 6.6+
It only applied cleanly to 6.16.y, so if you want it backported to older
kernels, please provide a working backport.
thanks,
greg k-h
prev parent reply other threads:[~2025-08-12 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 3:49 [PATCH ath-next 0/2] wifi: ath12k: install pairwise key first Baochen Qiang
2025-05-23 3:49 ` [PATCH ath-next 1/2] wifi: ath12k: avoid bit operation on key flags Baochen Qiang
2025-05-23 3:49 ` [PATCH ath-next 2/2] wifi: ath12k: install pairwise key first Baochen Qiang
2025-06-23 5:44 ` [PATCH ath-next 0/2] " Vasanthakumar Thiagarajan
2025-06-23 14:48 ` Jeff Johnson
2025-06-25 9:51 ` Johan Hovold
2025-06-25 10:15 ` Baochen Qiang
2025-06-25 14:48 ` Jeff Johnson
2025-06-25 14:57 ` Johan Hovold
2025-06-25 22:49 ` Jeff Johnson
2025-06-26 7:29 ` Greg KH
2025-08-12 15:58 ` Stable Request: " Jeff Johnson
2025-08-12 16:27 ` Greg KH [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=2025081240-trustless-secret-1354@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ath12k@lists.infradead.org \
--cc=gregoire.s93@live.fr \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@quicinc.com \
--cc=sre@kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.