From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [PATCH v41 09/13] crypto: provide access to a static Jitter RNG state
Date: Tue, 20 Jul 2021 14:13:39 +0800 [thread overview]
Message-ID: <202107201439.8IbX3Dt8-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3440 bytes --]
CC: kbuild-all(a)lists.01.org
In-Reply-To: <2275613.P25KImRyBb@positron.chronox.de>
References: <2275613.P25KImRyBb@positron.chronox.de>
TO: "Stephan Müller" <smueller@chronox.de>
TO: Tso Ted <tytso@mit.edu>
TO: linux-crypto(a)vger.kernel.org
CC: Willy Tarreau <w@1wt.eu>
CC: Nicolai Stange <nstange@suse.de>
CC: LKML <linux-kernel@vger.kernel.org>
CC: Arnd Bergmann <arnd@arndb.de>
CC: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
CC: "Eric W. Biederman" <ebiederm@xmission.com>
CC: "Alexander E. Patrakov" <patrakov@gmail.com>
CC: "Ahmed S. Darwish" <darwish.07@gmail.com>
Hi "Stephan,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on cryptodev/master crypto/master v5.14-rc2 next-20210719]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Stephan-M-ller/dev-random-a-new-approach/20210714-135308
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git 77d34a4683b053108ecd466cc7c4193b45805528
:::::: branch date: 6 days ago
:::::: commit date: 6 days ago
config: x86_64-randconfig-b001-20210714 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 8d69635ed9ecf36fd0ca85906bfde17949671cbe)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# apt-get install iwyu # include-what-you-use
# https://github.com/0day-ci/linux/commit/e6bc121044c3d2aa4e90f0c8564c7379a67e6055
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Stephan-M-ller/dev-random-a-new-approach/20210714-135308
git checkout e6bc121044c3d2aa4e90f0c8564c7379a67e6055
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross C=1 CHECK=iwyu O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
iwyu warnings: (new ones prefixed by >>)
>> crypto/jitterentropy.c:#include "crypto/internal/jitterentropy.h":1: iwyu: warning: superfluous #include "crypto/internal/jitterentropy.h"
--
>> crypto/jitterentropy-kcapi.c:#include "crypto/internal/jitterentropy.h":1: iwyu: warning: superfluous #include "crypto/internal/jitterentropy.h"
crypto/jitterentropy-kcapi.c:#include "crypto/internal/rng.h":1: iwyu: warning: superfluous #include "crypto/internal/rng.h"
>> crypto/jitterentropy-kcapi.c:46:1: iwyu: warning: superfluous #include <crypto/internal/jitterentropy.h>
crypto/jitterentropy-kcapi.c:45:1: iwyu: warning: superfluous #include <crypto/internal/rng.h>
crypto/jitterentropy-kcapi.c:40:1: iwyu: warning: superfluous #include <linux/kernel.h>
crypto/jitterentropy-kcapi.c:44:1: iwyu: warning: superfluous #include <linux/time.h>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 48785 bytes --]
next reply other threads:[~2021-07-20 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 6:13 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-14 5:43 [PATCH v41 00/13] /dev/random - a new approach Stephan Müller
2021-07-14 5:47 ` [PATCH v41 09/13] crypto: provide access to a static Jitter RNG state Stephan Müller
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=202107201439.8IbX3Dt8-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.