From: Mimi Zohar <zohar@linux.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-integrity@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Subject: Re: [PATCH] crypto: lib - Move mpi into lib/crypto
Date: Fri, 04 Aug 2023 10:24:57 -0400 [thread overview]
Message-ID: <7c288bb1bdc0a7c48ce5bd92c180f95ecbffcef9.camel@linux.ibm.com> (raw)
In-Reply-To: <ZMzD0q52dbeXNeaM@gondor.apana.org.au>
On Fri, 2023-08-04 at 17:24 +0800, Herbert Xu wrote:
> As lib/mpi is mostly used by crypto code, move it under lib/crypto
> so that patches touching it get directed to the right mailing list.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Thanks, Herbert.
Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
prev parent reply other threads:[~2023-08-04 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 9:24 [PATCH] crypto: lib - Move mpi into lib/crypto Herbert Xu
2023-08-04 14:24 ` Mimi Zohar [this message]
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=7c288bb1bdc0a7c48ce5bd92c180f95ecbffcef9.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dmitry.kasatkin@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox