From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, schnelle@linux.ibm.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y] s390/pci: Fix __pcilg_mio_inuser() inline assembly
Date: Wed, 25 Jun 2025 10:08:56 -0400 [thread overview]
Message-ID: <20250624192833-86b2ed42c775d7ef@stable.kernel.org> (raw)
In-Reply-To: <20250623110715.3446009-1-schnelle@linux.ibm.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: c4abe6234246c75cdc43326415d9cff88b7cf06c
WARNING: Author mismatch between patch and found commit:
Backport author: Niklas Schnelle<schnelle@linux.ibm.com>
Commit author: Heiko Carstens<hca@linux.ibm.com>
Status in newer kernel trees:
6.15.y | Present (different SHA1: 003d60f4f2af)
6.12.y | Present (different SHA1: 578d93d06043)
6.6.y | Present (different SHA1: cc789e07bb87)
6.1.y | Present (different SHA1: e0e15f95a393)
5.15.y | Present (different SHA1: a8814ec473c6)
Note: The patch differs from the upstream commit:
---
1: c4abe6234246c < -: ------------- s390/pci: Fix __pcilg_mio_inuser() inline assembly
-: ------------- > 1: 9a2f4b3653500 s390/pci: Fix __pcilg_mio_inuser() inline assembly
---
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:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 5:41 FAILED: patch "[PATCH] s390/pci: Fix __pcilg_mio_inuser() inline assembly" failed to apply to 5.10-stable tree gregkh
2025-06-23 11:07 ` [PATCH 5.10.y] s390/pci: Fix __pcilg_mio_inuser() inline assembly Niklas Schnelle
2025-06-25 14:08 ` 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=20250624192833-86b2ed42c775d7ef@stable.kernel.org \
--to=sashal@kernel.org \
--cc=schnelle@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 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.