From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Heiko Carstens <hca@linux.ibm.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y] s390: Add '-std=gnu11' to decompressor and purgatory CFLAGS
Date: Wed, 25 Jun 2025 10:09:00 -0400 [thread overview]
Message-ID: <20250624195532-505e3fa1210a6d89@stable.kernel.org> (raw)
In-Reply-To: <20250623134240.1107347-1-hca@linux.ibm.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: 3b8b80e993766dc96d1a1c01c62f5d15fafc79b9
WARNING: Author mismatch between patch and upstream commit:
Backport author: Heiko Carstens<hca@linux.ibm.com>
Commit author: Nathan Chancellor<nathan@kernel.org>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 593d852f7fe2)
6.6.y | Present (different SHA1: cefbf9f892ce)
6.1.y | Present (different SHA1: 62d33b9e68bd)
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: 3b8b80e993766 < -: ------------- s390: Add '-std=gnu11' to decompressor and purgatory CFLAGS
-: ------------- > 1: 1d0205496d23d s390: Add '-std=gnu11' to decompressor and purgatory CFLAGS
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y | Success | Success |
prev parent reply other threads:[~2025-06-25 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:42 [PATCH 5.10.y] s390: Add '-std=gnu11' to decompressor and purgatory CFLAGS Heiko Carstens
2025-06-25 14:09 ` 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=20250624195532-505e3fa1210a6d89@stable.kernel.org \
--to=sashal@kernel.org \
--cc=hca@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).