From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Danny Tsen <dtsen@linux.ibm.com>,
linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust file entries after crypto vmx file movement
Date: Thu, 8 Feb 2024 10:47:14 +0100 [thread overview]
Message-ID: <CAKXUXMynhktyTY8+JtDAuVHysV2g0eXy7dr09wvSqYxZ=paWUg@mail.gmail.com> (raw)
In-Reply-To: <ZbsxfYVKqxwn5gl5@gondor.apana.org.au>
On Thu, Feb 1, 2024 at 6:51 AM Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> On Mon, Jan 29, 2024 at 02:17:29PM +0100, Lukas Bulwahn wrote:
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 2fb944964be5..15bc79e80e28 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -10307,12 +10307,12 @@ M: Nayna Jain <nayna@linux.ibm.com>
> > M: Paulo Flabiano Smorigo <pfsmorigo@gmail.com>
> > L: linux-crypto@vger.kernel.org
> > S: Supported
> > -F: drivers/crypto/vmx/Kconfig
> > -F: drivers/crypto/vmx/Makefile
> > -F: drivers/crypto/vmx/aes*
> > -F: drivers/crypto/vmx/ghash*
> > -F: drivers/crypto/vmx/ppc-xlate.pl
> > -F: drivers/crypto/vmx/vmx.c
> > +F: arch/powerpc/crypto/Kconfig
> > +F: arch/powerpc/crypto/Makefile
> > +F: arch/powerpc/crypto/aes*
>
> Are you sure about this? There are non-vmx aes* files in that
> directory. Perhaps something more specific is needed here?
>
sorry for the late reply. I revisited this patch and now keep the
match exact in my patch v2:
https://lore.kernel.org/lkml/20240208093327.23926-1-lukas.bulwahn@gmail.com/
Herbert, I hope you are fine to pick this patch v2.
Lukas
prev parent reply other threads:[~2024-02-08 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 13:17 [PATCH] MAINTAINERS: adjust file entries after crypto vmx file movement Lukas Bulwahn
2024-02-01 5:51 ` Herbert Xu
2024-02-08 9:47 ` Lukas Bulwahn [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='CAKXUXMynhktyTY8+JtDAuVHysV2g0eXy7dr09wvSqYxZ=paWUg@mail.gmail.com' \
--to=lukas.bulwahn@gmail.com \
--cc=dtsen@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).