From: <ye.xingchen@zte.com.cn>
To: <herbert@gondor.apana.org.au>
Cc: <davem@davemloft.net>, <mpe@ellerman.id.au>, <npiggin@gmail.com>,
<christophe.leroy@csgroup.eu>, <linux-crypto@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH] crypto: p10-aes-gcm - remove duplicate include header
Date: Tue, 14 Mar 2023 16:31:51 +0800 (CST) [thread overview]
Message-ID: <202303141631511535639@zte.com.cn> (raw)
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>
---
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>
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: <ye.xingchen@zte.com.cn>
To: <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, npiggin@gmail.com,
linuxppc-dev@lists.ozlabs.org, davem@davemloft.net,
linux-crypto@vger.kernel.org
Subject: [PATCH] crypto: p10-aes-gcm - remove duplicate include header
Date: Tue, 14 Mar 2023 16:31:51 +0800 (CST) [thread overview]
Message-ID: <202303141631511535639@zte.com.cn> (raw)
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>
---
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>
--
2.25.1
next reply other threads:[~2023-03-14 8:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 8:31 ye.xingchen [this message]
2023-03-14 8:31 ` [PATCH] crypto: p10-aes-gcm - remove duplicate include header ye.xingchen
2023-03-14 8:47 ` Christophe Leroy
2023-03-14 8:47 ` Christophe Leroy
2023-03-14 8:49 ` Herbert Xu
2023-03-14 8:49 ` Herbert Xu
2023-03-14 10:44 ` Michael Ellerman
2023-03-14 10:44 ` Michael Ellerman
2023-03-15 3:35 ` Herbert Xu
2023-03-15 3:35 ` Herbert Xu
2023-03-16 3:58 ` Michael Ellerman
2023-03-16 3:58 ` Michael Ellerman
2023-03-16 4:03 ` Herbert Xu
2023-03-16 4:03 ` Herbert Xu
2023-03-24 10:28 ` 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=202303141631511535639@zte.com.cn \
--to=ye.xingchen@zte.com.cn \
--cc=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 \
/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.