From: Mark Brown <broonie@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Sami Tolvanen <samitolvanen@google.com>
Subject: Re: linux-next: manual merge of the keys-next tree with the modules tree
Date: Fri, 30 Jan 2026 18:11:55 +0000 [thread overview]
Message-ID: <c80f3db9-168f-4e05-b7a1-b1d4f702e9f0@sirena.org.uk> (raw)
In-Reply-To: <aXzoSci8NPhIwDf-@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
On Fri, Jan 30, 2026 at 05:20:09PM +0000, Mark Brown wrote:
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
Also needs this (or something):
From 6d9a82fe703a084c1dc0d5a1d184bea787aa7d9a Mon Sep 17 00:00:00 2001
From: Mark Brown <broonie@kernel.org>
Date: Fri, 30 Jan 2026 17:56:06 +0000
Subject: [PATCH] keys: Merge fixup
Signed-off-by: Mark Brown <broonie@kernel.org>
---
scripts/sign-file.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/sign-file.c b/scripts/sign-file.c
index a65c3e0c40b66..ef8a33ba9c529 100644
--- a/scripts/sign-file.c
+++ b/scripts/sign-file.c
@@ -206,6 +206,7 @@ int main(int argc, char **argv)
bool raw_sig = false;
unsigned char buf[4096];
unsigned long module_size, sig_size;
+ unsigned int use_signed_attrs = PKCS7_NOATTR;
const EVP_MD *digest_algo;
EVP_PKEY *private_key;
CMS_ContentInfo *cms = NULL;
--
2.47.3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2026-01-30 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 17:20 Mark Brown
2026-01-30 17:53 ` Sami Tolvanen
2026-01-30 18:06 ` Mark Brown
2026-01-30 18:13 ` Sami Tolvanen
2026-01-30 21:50 ` David Howells
2026-01-31 13:34 ` Mark Brown
2026-01-30 17:57 ` David Howells
2026-01-30 18:10 ` Sami Tolvanen
2026-01-30 21:56 ` David Howells
2026-01-30 22:59 ` Sami Tolvanen
2026-01-30 18:11 ` Mark Brown [this message]
2026-01-30 18:13 ` Sami Tolvanen
2026-01-30 18:18 ` Mark Brown
2026-02-03 19:18 Mark Brown
2026-02-03 19:26 ` Sami Tolvanen
2026-02-03 19:30 ` Mark Brown
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=c80f3db9-168f-4e05-b7a1-b1d4f702e9f0@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
/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
all inboxes | Powered by JetHome®