From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, giovanni.cabiddu@intel.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1] crypto: qat - fix ring to service map for QAT GEN4
Date: Thu, 17 Jul 2025 21:34:36 -0400 [thread overview]
Message-ID: <1752795908-8533c229@stable.kernel.org> (raw)
In-Reply-To: <20250717170835.25211-1-giovanni.cabiddu@intel.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found follow-up fixes in mainline
The upstream commit SHA1 provided is correct: a238487f7965d102794ed9f8aff0b667cd2ae886
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 82e4aa18bb6d)
Found fixes commits:
df018f82002a crypto: qat - fix ring to service map for dcc in 4xxx
Note: The patch differs from the upstream commit:
---
1: a238487f7965 < -: ------------ crypto: qat - fix ring to service map for QAT GEN4
-: ------------ > 1: 1c3a13c46a06 crypto: qat - fix ring to service map for QAT GEN4
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2025-07-18 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 17:06 [PATCH 6.1] crypto: qat - fix ring to service map for QAT GEN4 Giovanni Cabiddu
2025-07-18 1:34 ` Sasha Levin [this message]
2025-07-18 6:54 ` Giovanni Cabiddu
2025-07-18 12:11 ` Sasha Levin
2025-07-22 9:42 ` Greg KH
2025-07-22 13:29 ` Giovanni Cabiddu
2025-07-22 13:39 ` Greg KH
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=1752795908-8533c229@stable.kernel.org \
--to=sashal@kernel.org \
--cc=giovanni.cabiddu@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