From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: jianqi.ren.cn@windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] wifi: cfg80211: check A-MSDU format more carefully
Date: Tue, 13 May 2025 14:51:17 -0400 [thread overview]
Message-ID: <20250513095419-51d121afa8dba725@stable.kernel.org> (raw)
In-Reply-To: <20250513020938.3361430-1-jianqi.ren.cn@windriver.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 9ad7974856926129f190ffbe3beea78460b3b7cc
WARNING: Author mismatch between patch and upstream commit:
Backport author: <jianqi.ren.cn@windriver.com>
Commit author: Johannes Berg<johannes.berg@intel.com>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 5d7a8585fbb3)
6.1.y | Present (different SHA1: 9eb3bc0973d0)
Note: The patch differs from the upstream commit:
---
1: 9ad7974856926 < -: ------------- wifi: cfg80211: check A-MSDU format more carefully
-: ------------- > 1: af32816746f4e wifi: cfg80211: check A-MSDU format more carefully
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-05-13 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 2:09 [PATCH 5.15.y] wifi: cfg80211: check A-MSDU format more carefully jianqi.ren.cn
2025-05-13 18:51 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-13 2:06 jianqi.ren.cn
2025-05-13 18:50 ` Sasha Levin
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=20250513095419-51d121afa8dba725@stable.kernel.org \
--to=sashal@kernel.org \
--cc=jianqi.ren.cn@windriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox