From: Andrew Morton <akpm@linux-foundation.org>
To: Alexander Potapenko <glider@google.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Robert Elliott <elliott@hpe.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: [PATCH -next 1/2] x86: crypto: kmsan: revert !KMSAN dependencies
Date: Tue, 13 Sep 2022 17:52:10 -0700 [thread overview]
Message-ID: <20220913175210.50945edb0738bf95300dc500@linux-foundation.org> (raw)
In-Reply-To: <20220909095811.2166073-1-glider@google.com>
On Fri, 9 Sep 2022 11:58:10 +0200 Alexander Potapenko <glider@google.com> wrote:
> This patch reverts "crypto: Kconfig: fix up for "crypto: kmsan: disable
> accelerated configs under KMSAN" used by Stephen Rothwell to cleanly
> merge KMSAN patches into linux-next.
>
> Because now arch-specific crypto configs reside in a separate Kconfig
> file, we can disable them all by adding a single !KMSAN before including
> that file (done in the following patch).
>
> Among others, this patch reverts !KMSAN check for
> CONFIG_CRYPTO_AEGIS128_SIMD, which is ARM-only and is hence unnecessary,
> because KMSAN does not support ARM yet.
As I understand it, these patches are against linux-next and only
linux-next because they pertain to linux-next's resolution of conflicts
between the MM tree and the crypto tree?
I'm not sure how to handle that, even if anyone wants to. How about
you send an update to
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm's mm-unstable
branch so the code which is there makes sense? Then we'll ask Stephen
to redo the crypto tree resolution?
next prev parent reply other threads:[~2022-09-14 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 9:58 [PATCH -next 1/2] x86: crypto: kmsan: revert !KMSAN dependencies Alexander Potapenko
2022-09-09 9:58 ` [PATCH -next 2/2] crypto: x86: kmsan: disable accelerated configs in KMSAN builds Alexander Potapenko
2022-09-16 9:23 ` Alexander Potapenko
2022-09-18 21:45 ` Stephen Rothwell
2022-09-14 0:52 ` Andrew Morton [this message]
2022-09-14 8:18 ` [PATCH -next 1/2] x86: crypto: kmsan: revert !KMSAN dependencies Alexander Potapenko
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=20220913175210.50945edb0738bf95300dc500@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ebiggers@kernel.org \
--cc=elliott@hpe.com \
--cc=glider@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.