[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG_fn=V1utoSbPK6Jhnzyy3Fj47k1YS1DZc5M094Bp1GpP5kFQ@mail.gmail.com>
Date: Mon, 12 Sep 2022 11:37:56 +0200
From: Alexander Potapenko <glider@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Eric Biggers <ebiggers@...nel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Herbert Xu <herbert@...dor.apana.org.au>,
Linux Crypto List <linux-crypto@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Robert Elliott <elliott@....com>
Subject: Re: linux-next: manual merge of the mm tree with the crypto tree
On Wed, Sep 7, 2022 at 10:41 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Wed, 7 Sep 2022 11:18:24 +0200 Alexander Potapenko <glider@...gle.com> wrote:
>
> > What's the best way to handle this? Send another patch series? Or
> > maybe just an update for "crypto: kmsan: disable accelerated configs
> > under KMSAN"?
>
> I'd prefer the minimal update, please.
As a heads-up, I mailed "x86: crypto: kmsan: revert !KMSAN
dependencies" and "crypto: x86: kmsan: disable accelerated configs in
KMSAN builds" last week. No rush though, guess you're busy with LPC
this week.
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Paul Manicle, Liana Sebastian
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Powered by blists - more mailing lists