From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Zenm Chen <zenmchen@gmail.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6.y 1/2] wifi: rtw89: pci: add pre_deinit to be called after probe complete
Date: Thu, 13 Mar 2025 05:01:42 -0400 [thread overview]
Message-ID: <20250312222401-376773b9df78d3a1@stable.kernel.org> (raw)
In-Reply-To: <20250311081001.1394-2-zenmchen@gmail.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: 9e1aff437a560cd72cb6a60ee33fe162b0afdaf1
WARNING: Author mismatch between patch and upstream commit:
Backport author: Zenm Chen<zenmchen@gmail.com>
Commit author: Ping-Ke Shih<pkshih@realtek.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
1: 9e1aff437a560 < -: ------------- wifi: rtw89: pci: add pre_deinit to be called after probe complete
-: ------------- > 1: 1b950ee5b56cc wifi: rtw89: pci: add pre_deinit to be called after probe complete
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
next prev parent reply other threads:[~2025-03-13 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 8:09 [PATCH 6.6.y 0/2] wifi: rtw89: RTL8852BE: Fix the shutdown issue Zenm Chen
2025-03-11 8:10 ` [PATCH 6.6.y 1/2] wifi: rtw89: pci: add pre_deinit to be called after probe complete Zenm Chen
2025-03-13 9:01 ` Sasha Levin [this message]
2025-03-13 16:08 ` Greg KH
2025-03-13 20:38 ` [PATCH 6.6.y 1/2] wifi: rtw89: pci: add pre_deinit to be called Zenm Chen
2025-03-11 8:10 ` [PATCH 6.6.y 2/2] wifi: rtw89: pci: disable PCIE wake bit when PCIE deinit Zenm Chen
2025-03-13 9:01 ` 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=20250312222401-376773b9df78d3a1@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zenmchen@gmail.com \
/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.