From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: WangYuli <wangyuli@uniontech.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1/6.6] MIPS: mipsregs: Set proper ISA level for virt extensions
Date: Wed, 25 Dec 2024 20:21:46 -0500 [thread overview]
Message-ID: <20241225174433-a6ea649ee16c8b60@stable.kernel.org> (raw)
In-Reply-To: <38A42FE743EFB36A+20241224062239.19248-1-wangyuli@uniontech.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: a640d6762a7d404644201ebf6d2a078e8dc84f97
WARNING: Author mismatch between patch and upstream commit:
Backport author: WangYuli <wangyuli@uniontech.com>
Commit author: Jiaxun Yang <jiaxun.yang@flygoat.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: a640d6762a7d ! 1: b6d3079a55fb MIPS: mipsregs: Set proper ISA level for virt extensions
@@ Metadata
## Commit message ##
MIPS: mipsregs: Set proper ISA level for virt extensions
+ [ Upstream commit a640d6762a7d404644201ebf6d2a078e8dc84f97 ]
+
c994a3ec7ecc ("MIPS: set mips32r5 for virt extensions") setted
some instructions in virt extensions to ISA level mips32r5.
@@ Commit message
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
+ Signed-off-by: WangYuli <wangyuli@uniontech.com>
## arch/mips/include/asm/mipsregs.h ##
@@ arch/mips/include/asm/mipsregs.h: do { \
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2024-12-26 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 6:22 [PATCH 6.1/6.6] MIPS: mipsregs: Set proper ISA level for virt extensions WangYuli
2024-12-26 1:21 ` Sasha Levin [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=20241225174433-a6ea649ee16c8b60@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wangyuli@uniontech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox