From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [cryptodev:master 110/119] drivers/crypto/gemini/sl3516-ce-cipher.c: linux/io.h is included more than once.
Date: Fri, 11 Jun 2021 17:08:02 +0800 [thread overview]
Message-ID: <202106111714.8a43PF68-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1049 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
tree: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
head: 0dc64297c8ac98503a7c7621b3c78e151deb75b6
commit: 46c5338db7bd45b2cf99570560f00389d60fd6b4 [110/119] crypto: sl3516 - Add sl3516 crypto engine
:::::: branch date: 2 hours ago
:::::: commit date: 2 hours ago
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
includecheck warnings: (new ones prefixed by >>)
>> drivers/crypto/gemini/sl3516-ce-cipher.c: linux/io.h is included more than once.
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2021-06-11 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 9:08 kernel test robot [this message]
2021-06-11 9:08 ` [RFC PATCH cryptodev] crypto: fix duplicated inclusion kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 1:30 [cryptodev:master 110/119] drivers/crypto/gemini/sl3516-ce-cipher.c: linux/io.h is included more than once kernel test robot
2021-06-15 1:30 ` kernel test robot
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=202106111714.8a43PF68-lkp@intel.com \
--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.