From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Eric Biggers <ebiggers@kernel•org>,
"Jason A. Donenfeld" <Jason@zx2c4•com>,
Ard Biesheuvel <ardb@kernel•org>,
Linux Crypto List <linux-crypto@vger•kernel.org>,
Vasily Gorbik <gor@linux•ibm.com>,
Christian Borntraeger <borntraeger@de•ibm.com>
Cc: Alexander Gordeev <agordeev@linux•ibm.com>,
Heiko Carstens <hca@linux•ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: manual merge of the libcrypto tree with the s390 tree
Date: Fri, 4 Jul 2025 14:16:35 +1000 [thread overview]
Message-ID: <20250704141635.57ff7b16@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
Hi all,
Today's linux-next merge of the libcrypto tree got a conflict in:
arch/s390/lib/crypto/sha256.c
between commit:
65c9a9f92502 ("s390: Explicitly include <linux/export.h>")
from the s390 tree and commit:
1a8f59dfdca0 ("lib/crypto: sha256: Consolidate into single module")
b8456f7aaf35 ("lib/crypto: s390: Move arch/s390/lib/crypto/ into lib/crypto/")
from the libcrypto tree.
I fixed it up (I removed the file) 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-07-04 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 4:16 Stephen Rothwell [this message]
2025-07-29 23:05 ` linux-next: manual merge of the libcrypto tree with the s390 tree 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=20250704141635.57ff7b16@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Jason@zx2c4$(echo .)com \
--cc=agordeev@linux$(echo .)ibm.com \
--cc=ardb@kernel$(echo .)org \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=ebiggers@kernel$(echo .)org \
--cc=gor@linux$(echo .)ibm.com \
--cc=hca@linux$(echo .)ibm.com \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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