public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alexander Potapenko <glider@google•com>
Cc: Andrew Morton <akpm@linux-foundation•org>,
	Eric Biggers <ebiggers@kernel•org>,
	Herbert Xu <herbert@gondor•apana.org.au>,
	Robert Elliott <elliott@hpe•com>,
	Linux Crypto List <linux-crypto@vger•kernel.org>,
	LKML <linux-kernel@vger•kernel.org>,
	linux-next <linux-next@vger•kernel.org>
Subject: Re: [PATCH -next 2/2] crypto: x86: kmsan: disable accelerated configs in KMSAN builds
Date: Mon, 19 Sep 2022 07:45:21 +1000	[thread overview]
Message-ID: <20220919074521.5c2b22c0@canb.auug.org.au> (raw)
In-Reply-To: <CAG_fn=UT24yoY=amdXF5gXQjM9jw8bMamjC-mqJndiXNtNhvLA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 364 bytes --]

Hi Alexander,

On Fri, 16 Sep 2022 11:23:47 +0200 Alexander Potapenko <glider@google•com> wrote:
>
> Please use this patch to replace "crypto: x86: kmsan: disable
> accelerated configs in KMSAN builds" when merging linux-mm into
> linux-next (assuming arch/x86/crypto/Kconfig is still in -next).

OK, will do from today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-09-18 21:45 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 [this message]
2022-09-14  0:52 ` [PATCH -next 1/2] x86: crypto: kmsan: revert !KMSAN dependencies Andrew Morton
2022-09-14  8:18   ` 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=20220919074521.5c2b22c0@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=ebiggers@kernel$(echo .)org \
    --cc=elliott@hpe$(echo .)com \
    --cc=glider@google$(echo .)com \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --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