From: Herbert Xu <herbert@gondor.apana.org.au>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Breno Leitão" <leitao@debian.org>,
"David S. Miller" <davem@davemloft.net>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Nayna Jain" <nayna@linux.ibm.com>,
"Paul Mackerras" <paulus@samba.org>,
"Paulo Flabiano Smorigo" <pfsmorigo@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] crypto: vmx - Align the short log with Makefile cleanups
Date: Fri, 6 May 2022 18:23:22 +0800 [thread overview]
Message-ID: <YnT3GtU975OsXVuN@gondor.apana.org.au> (raw)
In-Reply-To: <20220501130749.1123387-1-masahiroy@kernel.org>
On Sun, May 01, 2022 at 10:07:49PM +0900, Masahiro Yamada wrote:
> I notieced the log is not properly aligned:
>
> PERL drivers/crypto/vmx/aesp8-ppc.S
> CC [M] fs/xfs/xfs_reflink.o
> PERL drivers/crypto/vmx/ghashp8-ppc.S
> CC [M] drivers/crypto/vmx/aes.o
>
> Add some spaces after 'PERL'.
>
> While I was here, I cleaned up the Makefile:
>
> - Merge the two similar rules
>
> - Remove redundant 'clean-files' (Having 'targets' is enough)
>
> - Move the flavour into the build command
>
> This still avoids the build failures fixed by commit 4ee812f6143d
> ("crypto: vmx - Avoid weird build failures").
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> drivers/crypto/vmx/Makefile | 17 +++--------------
> 1 file changed, 3 insertions(+), 14 deletions(-)
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2022-05-06 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 13:07 [PATCH] crypto: vmx - Align the short log with Makefile cleanups Masahiro Yamada
2022-05-03 13:01 ` kernel test robot
2022-05-06 10:23 ` Herbert Xu [this message]
2022-05-06 15:25 ` Masahiro Yamada
2022-05-07 2:02 ` Herbert Xu
2022-05-07 5:24 ` Masahiro Yamada
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=YnT3GtU975OsXVuN@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=leitao@debian.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nayna@linux.ibm.com \
--cc=paulus@samba.org \
--cc=pfsmorigo@gmail.com \
/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).