From: Andrew Morton <akpm@linux-foundation.org>
To: Alexander Potapenko <glider@google.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto List <linux-crypto@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Robert Elliott <elliott@hpe.com>
Subject: Re: linux-next: manual merge of the mm tree with the crypto tree
Date: Mon, 12 Sep 2022 11:59:24 -0700 [thread overview]
Message-ID: <20220912115924.e04b9505994c3053232bbb8a@linux-foundation.org> (raw)
In-Reply-To: <CAG_fn=V1utoSbPK6Jhnzyy3Fj47k1YS1DZc5M094Bp1GpP5kFQ@mail.gmail.com>
On Mon, 12 Sep 2022 11:37:56 +0200 Alexander Potapenko <glider@google.com> wrote:
> On Wed, Sep 7, 2022 at 10:41 PM Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > On Wed, 7 Sep 2022 11:18:24 +0200 Alexander Potapenko <glider@google.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.
oop. sorry, things starting with "x86: " and "crypto: " tend to hit my
not-for-akpm brainfilter. I have them now.
next prev parent reply other threads:[~2022-09-12 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 10:20 linux-next: manual merge of the mm tree with the crypto tree Stephen Rothwell
2022-09-06 22:12 ` Eric Biggers
2022-09-07 9:18 ` Alexander Potapenko
2022-09-07 20:41 ` Andrew Morton
2022-09-12 9:37 ` Alexander Potapenko
2022-09-12 18:59 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-18 9:53 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=20220912115924.e04b9505994c3053232bbb8a@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.