From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, chenhuacai@loongson.cn
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1&6.6 1/3] sign-file,extract-cert: move common SSL helper functions to a header
Date: Tue, 18 Mar 2025 11:13:01 -0400 [thread overview]
Message-ID: <20250318074754-5b4ba3b2d09516b3@stable.kernel.org> (raw)
In-Reply-To: <20250318105308.2160738-2-chenhuacai@loongson.cn>
[ 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: 300e6d4116f956b035281ec94297dc4dc8d4e1d3
WARNING: Author mismatch between patch and found 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: fcefe79724945 sign-file,extract-cert: move common SSL helper functions to a 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 |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
next prev parent reply other threads:[~2025-03-18 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:53 [PATCH 6.1&6.6 0/3] sign-file,extract-cert: switch to PROVIDER API for OpenSSL >= 3.0 Huacai Chen
2025-03-18 10:53 ` [PATCH 6.1&6.6 1/3] sign-file,extract-cert: move common SSL helper functions to a header Huacai Chen
2025-03-18 10:54 ` kernel test robot
2025-03-18 15:13 ` Sasha Levin [this message]
2025-03-18 10:53 ` [PATCH 6.1&6.6 2/3] sign-file,extract-cert: avoid using deprecated ERR_get_error_line() Huacai Chen
2025-03-18 15:12 ` Sasha Levin
2025-03-18 10:53 ` [PATCH 6.1&6.6 3/3] sign-file,extract-cert: use pkcs11 provider for OPENSSL MAJOR >= 3 Huacai Chen
2025-03-18 15:12 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2025-03-18 11:01 [PATCH 6.1&6.6 V2 0/3] sign-file,extract-cert: switch to PROVIDER API for OpenSSL >= 3.0 Huacai Chen
2025-03-18 11:01 ` [PATCH 6.1&6.6 1/3] sign-file,extract-cert: move common SSL helper functions to a header Huacai Chen
2025-03-18 13:24 ` Greg Kroah-Hartman
2025-03-18 13:58 ` Huacai Chen
2025-03-18 14:37 ` Greg Kroah-Hartman
2025-03-19 4:34 ` Huacai Chen
2025-03-18 15:12 ` Sasha Levin
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=20250318074754-5b4ba3b2d09516b3@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