From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [RFC PATCH cryptodev] crypto: fix duplicated inclusion
Date: Fri, 11 Jun 2021 17:08:09 +0800 [thread overview]
Message-ID: <20210611090809.GA116398@2ceae6d31e96> (raw)
In-Reply-To: <202106111714.8a43PF68-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-crypto(a)vger.kernel.org
TO: Corentin Labbe <clabbe@baylibre.com>
CC: Herbert Xu <herbert@gondor.apana.org.au>
CC: Linus Walleij <linus.walleij@linaro.org>
CC: linux-crypto(a)vger.kernel.org
CC: linux-kernel(a)vger.kernel.org
drivers/crypto/gemini/sl3516-ce-cipher.c: linux/io.h is included more than once.
Generated by: scripts/checkincludes.pl
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
sl3516-ce-cipher.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/crypto/gemini/sl3516-ce-cipher.c b/drivers/crypto/gemini/sl3516-ce-cipher.c
index 0b34a4971e498..b41c2f5fc495a 100644
--- a/drivers/crypto/gemini/sl3516-ce-cipher.c
+++ b/drivers/crypto/gemini/sl3516-ce-cipher.c
@@ -12,7 +12,6 @@
#include <linux/dma-mapping.h>
#include <linux/delay.h>
#include <linux/io.h>
-#include <linux/io.h>
#include <linux/pm_runtime.h>
#include <crypto/scatterwalk.h>
#include <crypto/internal/skcipher.h>
next prev parent reply other threads:[~2021-06-11 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 9:08 [cryptodev:master 110/119] drivers/crypto/gemini/sl3516-ce-cipher.c: linux/io.h is included more than once kernel test robot
2021-06-11 9:08 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 1:30 kernel test robot
2021-06-15 1:31 ` [RFC PATCH cryptodev] crypto: fix duplicated inclusion kernel test robot
2021-06-15 1:31 ` kernel test robot
2021-06-24 7:33 ` Herbert Xu
2021-06-24 7:33 ` 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=20210611090809.GA116398@2ceae6d31e96 \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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 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.