mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "ye.xingchen@zte.com.cn" <ye.xingchen@zte.com.cn>,
	"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
	"npiggin@gmail.com" <npiggin@gmail.com>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: p10-aes-gcm - remove duplicate include header
Date: Tue, 14 Mar 2023 08:47:30 +0000	[thread overview]
Message-ID: <dbbd6ff3-5e17-9b63-9027-359e37ace668@csgroup.eu> (raw)
In-Reply-To: <202303141631511535639@zte.com.cn>

Hi,

Le 14/03/2023 à 09:31, ye.xingchen@zte.com.cn a écrit :
> From: Ye Xingchen <ye.xingchen@zte.com.cn>
> 
> crypto/algapi.h is included more than once.
> 
> Signed-off-by: Ye Xingchen <ye.xingchen@zte.com.cn>

You already sent this patch, see 
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/202301171601080312252@zte.com.cn/

Any reason for resending ?

Christophe


> ---
>   arch/powerpc/crypto/aes-gcm-p10-glue.c | 1 -
>   1 file changed, 1 deletion(-)
> 
> diff --git a/arch/powerpc/crypto/aes-gcm-p10-glue.c b/arch/powerpc/crypto/aes-gcm-p10-glue.c
> index c95f5b7cc456..1533c8cdd26f 100644
> --- a/arch/powerpc/crypto/aes-gcm-p10-glue.c
> +++ b/arch/powerpc/crypto/aes-gcm-p10-glue.c
> @@ -8,7 +8,6 @@
>   #include <asm/unaligned.h>
>   #include <asm/simd.h>
>   #include <asm/switch_to.h>
> -#include <crypto/algapi.h>
>   #include <crypto/aes.h>
>   #include <crypto/algapi.h>
>   #include <crypto/b128ops.h>

  reply	other threads:[~2023-03-14  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14  8:31 ye.xingchen
2023-03-14  8:47 ` Christophe Leroy [this message]
2023-03-14  8:49   ` Herbert Xu
2023-03-14 10:44     ` Michael Ellerman
2023-03-15  3:35       ` Herbert Xu
2023-03-16  3:58         ` Michael Ellerman
2023-03-16  4:03           ` Herbert Xu
2023-03-24 10:28 ` Herbert Xu

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=dbbd6ff3-5e17-9b63-9027-359e37ace668@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=ye.xingchen@zte.com.cn \
    /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
all inboxes | Powered by JetHome®