From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Jason Andryuk <jason.andryuk@amd.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 1/2] x86/xen: move xen_reserve_extra_memory()
Date: Sun, 13 Apr 2025 12:47:04 -0400 [thread overview]
Message-ID: <20250412122501-c369a62fdc5c5069@stable.kernel.org> (raw)
In-Reply-To: <20250411165122.18587-2-jason.andryuk@amd.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: fc05ea89c9ab45e70cb73e70bc0b9cdd403e0ee1
WARNING: Author mismatch between patch and upstream commit:
Backport author: Jason Andryuk<jason.andryuk@amd.com>
Commit author: Roger Pau Monne<roger.pau@citrix.com>
Note: The patch differs from the upstream commit:
---
1: fc05ea89c9ab4 < -: ------------- x86/xen: move xen_reserve_extra_memory()
-: ------------- > 1: 9bc5c94e278f7 Linux 6.14.2
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y | Success | Success |
next prev parent reply other threads:[~2025-04-13 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 16:51 [PATCH 0/2] Stable-6.6 backport x86/xen: fix memblock_reserve() usage on PVH Jason Andryuk
2025-04-11 16:51 ` [PATCH 1/2] x86/xen: move xen_reserve_extra_memory() Jason Andryuk
2025-04-13 16:47 ` Sasha Levin [this message]
2025-04-11 16:51 ` [PATCH 2/2] x86/xen: fix memblock_reserve() usage on PVH Jason Andryuk
2025-04-13 16:46 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2024-07-25 7:31 [PATCH 0/2] " Roger Pau Monne
2024-07-25 7:31 ` [PATCH 1/2] x86/xen: move xen_reserve_extra_memory() Roger Pau Monne
2024-07-25 8:02 ` Jürgen Groß
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=20250412122501-c369a62fdc5c5069@stable.kernel.org \
--to=sashal@kernel.org \
--cc=jason.andryuk@amd.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 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.