From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1 3/3] x86/its: Fix build errors when CONFIG_MODULES=n
Date: Wed, 14 May 2025 16:13:58 -0400 [thread overview]
Message-ID: <20250514103913-be7bb918882f7725@stable.kernel.org> (raw)
In-Reply-To: <20250513-its-fixes-6-1-v1-3-757b4ab02c79@linux.intel.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: 9f35e33144ae5377d6a8de86dd3bd4d995c6ac65
WARNING: Author mismatch between patch and upstream commit:
Backport author: Pawan Gupta<pawan.kumar.gupta@linux.intel.com>
Commit author: Eric Biggers<ebiggers@google.com>
Status in newer kernel trees:
6.14.y | Not found
6.12.y | Not found
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: 9f35e33144ae5 < -: ------------- x86/its: Fix build errors when CONFIG_MODULES=n
-: ------------- > 1: 02b72ccb5f9df Linux 6.1.138
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-05-14 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 5:35 [PATCH 6.1 0/3] ITS fixes Pawan Gupta
2025-05-14 5:35 ` [PATCH 6.1 1/3] x86/alternative: Optimize returns patching Pawan Gupta
2025-05-14 20:13 ` Sasha Levin
2025-05-14 5:36 ` [PATCH 6.1 2/3] x86/alternatives: Remove faulty optimization Pawan Gupta
2025-05-14 20:14 ` Sasha Levin
2025-05-14 5:36 ` [PATCH 6.1 3/3] x86/its: Fix build errors when CONFIG_MODULES=n Pawan Gupta
2025-05-14 20:13 ` 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=20250514103913-be7bb918882f7725@stable.kernel.org \
--to=sashal@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.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