From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Huacai Chen <chenhuacai@loongson.cn>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1&6.6 V3 1/3] sign-file,extract-cert: move common SSL helper functions to a header
Date: Wed, 19 Mar 2025 06:54:19 -0400 [thread overview]
Message-ID: <20250319051903-1c9549413af290f2@stable.kernel.org> (raw)
In-Reply-To: <20250319064031.2971073-2-chenhuacai@loongson.cn>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 300e6d4116f956b035281ec94297dc4dc8d4e1d3
WARNING: Author mismatch between patch and upstream commit:
Backport author: Huacai Chen<chenhuacai@loongson.cn>
Commit author: Jan Stancek<jstancek@redhat.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: 300e6d4116f95 ! 1: feb32525515c2 sign-file,extract-cert: move common SSL helper functions to a header
@@ Metadata
## Commit message ##
sign-file,extract-cert: move common SSL helper functions to a header
+ commit 300e6d4116f956b035281ec94297dc4dc8d4e1d3 upstream.
+
Couple error handling helpers are repeated in both tools, so
move them to a common header.
@@ Commit message
Tested-by: R Nageswara Sastry <rnsastry@linux.ibm.com>
Reviewed-by: Neal Gompa <neal@gompa.dev>
Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
+ Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
## MAINTAINERS ##
@@ MAINTAINERS: S: Maintained
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| Current branch | Success | Success |
next prev parent reply other threads:[~2025-03-19 10:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 6:40 [PATCH 6.1&6.6 V3 0/3] sign-file,extract-cert: switch to PROVIDER API for OpenSSL >= 3.0 Huacai Chen
2025-03-19 6:40 ` [PATCH 6.1&6.6 V3 1/3] sign-file,extract-cert: move common SSL helper functions to a header Huacai Chen
2025-03-19 10:54 ` Sasha Levin [this message]
2025-03-19 6:40 ` [PATCH 6.1&6.6 V3 2/3] sign-file,extract-cert: avoid using deprecated ERR_get_error_line() Huacai Chen
2025-03-19 10:54 ` Sasha Levin
2025-03-19 6:40 ` [PATCH 6.1&6.6 V3 3/3] sign-file,extract-cert: use pkcs11 provider for OPENSSL MAJOR >= 3 Huacai Chen
2025-03-19 10:54 ` Sasha Levin
2025-03-19 14:13 ` Greg Kroah-Hartman
2025-03-19 14:44 ` Jan Stancek
2025-03-19 16:25 ` Greg Kroah-Hartman
2025-03-19 16:53 ` Jan Stancek
2025-03-20 3:01 ` Huacai Chen
2025-03-30 13:07 ` Huacai Chen
2025-03-30 13:40 ` Jan Stancek
2025-04-14 13:52 ` Huacai Chen
2025-04-22 7:53 ` Greg Kroah-Hartman
2025-04-22 12:30 ` Huacai Chen
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=20250319051903-1c9549413af290f2@stable.kernel.org \
--to=sashal@kernel.org \
--cc=chenhuacai@loongson.cn \
--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