From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jarkko Sakkinen <jarkko@kernel•org>,
Masahiro Yamada <masahiroy@kernel•org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>,
"Mickaël Salaün" <mic@linux•microsoft.com>
Subject: linux-next: manual merge of the tpmdd tree with the kbuild tree
Date: Fri, 7 Jan 2022 15:33:06 +1100 [thread overview]
Message-ID: <20220107153306.3f8a2329@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
Hi all,
Today's linux-next merge of the tpmdd tree got a conflict in:
MAINTAINERS
certs/.gitignore
between commit:
98bb79d61f0c ("certs: move scripts/extract-cert to certs/")
from the kbuild tree and commit:
0fde37e9c004 ("certs: Check that builtin blacklist hashes are valid")
from the tpmdd tree.
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.
--
Cheers,
Stephen Rothwell
diff --cc MAINTAINERS
index d38fd8f77cbc,f8188efa3854..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -4445,7 -4410,10 +4445,9 @@@ L: keyrings@vger•kernel.or
S: Maintained
F: Documentation/admin-guide/module-signing.rst
F: certs/
+ F: scripts/check-blacklist-hashes.awk
-F: scripts/extract-cert.c
F: scripts/sign-file.c
+ F: tools/certs/
CFAG12864B LCD DRIVER
M: Miguel Ojeda <ojeda@kernel•org>
diff --cc certs/.gitignore
index 9e42fe3e02f5,01de9442e4e2..000000000000
--- a/certs/.gitignore
+++ b/certs/.gitignore
@@@ -1,4 -1,4 +1,5 @@@
# SPDX-License-Identifier: GPL-2.0-only
+ /blacklist_hashes_checked
+/extract-cert
/x509_certificate_list
/x509_revocation_list
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-01-07 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 4:33 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-07 4:43 linux-next: manual merge of the tpmdd tree with the kbuild tree Stephen Rothwell
2019-11-18 1:39 Stephen Rothwell
2019-11-26 20:32 ` Stephen Rothwell
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=20220107153306.3f8a2329@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jarkko@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=masahiroy@kernel$(echo .)org \
--cc=mic@linux$(echo .)microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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