From: kernel test robot <lkp@intel.com>
To: LeoLiu-oc <LeoLiu-oc@zhaoxin.com>,
olivia@selenic.com, herbert@gondor.apana.org.au,
jiajie.ho@starfivetech.com, conor.dooley@microchip.com,
martin@kaiser.cx, mmyangfl@gmail.com,
jenny.zhang@starfivetech.com, robh@kernel.org,
l.stelmach@samsung.com, ardb@kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, CobeChen@zhaoxin.com,
TonyWWang@zhaoxin.com, YunShen@zhaoxin.com, LeoLiu@zhaoxin.com,
LeoLiuoc <LeoLiu-oc@zhaoxin.com>
Subject: Re: [PATCH v4] hwrng: add Zhaoxin rng driver base on rep_xstore instruction
Date: Tue, 26 Dec 2023 09:04:23 +0800 [thread overview]
Message-ID: <202312260844.FPx3YOsI-lkp@intel.com> (raw)
In-Reply-To: <20231225025330.809554-1-LeoLiu-oc@zhaoxin.com>
Hi LeoLiu-oc,
kernel test robot noticed the following build errors:
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on char-misc/char-misc-next char-misc/char-misc-linus herbert-cryptodev-2.6/master linus/master v6.7-rc7 next-20231222]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/LeoLiu-oc/hwrng-add-Zhaoxin-rng-driver-base-on-rep_xstore-instruction/20231225-153520
base: char-misc/char-misc-testing
patch link: https://lore.kernel.org/r/20231225025330.809554-1-LeoLiu-oc%40zhaoxin.com
patch subject: [PATCH v4] hwrng: add Zhaoxin rng driver base on rep_xstore instruction
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20231226/202312260844.FPx3YOsI-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231226/202312260844.FPx3YOsI-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312260844.FPx3YOsI-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/char/hw_random/via-rng.c:220:26: error: conflicting types for 'via_rng_cpu_id'; have 'struct x86_cpu_id[]'
220 | static struct x86_cpu_id via_rng_cpu_id[] = {
| ^~~~~~~~~~~~~~
drivers/char/hw_random/via-rng.c:38:32: note: previous declaration of 'via_rng_cpu_id' with type 'const struct x86_cpu_id[]'
38 | static const struct x86_cpu_id via_rng_cpu_id[];
| ^~~~~~~~~~~~~~
drivers/char/hw_random/via-rng.c:38:32: warning: array 'via_rng_cpu_id' assumed to have one element
vim +220 drivers/char/hw_random/via-rng.c
219
> 220 static struct x86_cpu_id via_rng_cpu_id[] = {
221 X86_MATCH_VENDOR_FAM_FEATURE(CENTAUR, 6, X86_FEATURE_XSTORE, NULL),
222 {}
223 };
224 MODULE_DEVICE_TABLE(x86cpu, via_rng_cpu_id);
225
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-26 1:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 7:09 [PATCH] hwrng: add Zhaoxin rng driver base on rep_xstore instruction LeoLiu-oc
2023-11-07 16:29 ` kernel test robot
2023-11-08 7:34 ` [PATCH v2] " LeoLiu-oc
2023-11-17 10:35 ` Herbert Xu
2023-11-17 11:19 ` LeoLiu-oc
2023-11-21 3:29 ` LeoLiu-oc
2023-12-01 9:31 ` Herbert Xu
2023-12-05 3:41 ` LeoLiu-oc
2023-12-01 9:34 ` Herbert Xu
2023-12-05 3:47 ` LeoLiu-oc
2023-12-01 9:38 ` Herbert Xu
2023-12-05 6:56 ` LeoLiu-oc
2023-12-21 6:26 ` [PATCH v3] " LeoLiu-oc
2023-12-23 0:11 ` kernel test robot
2023-12-23 0:21 ` kernel test robot
2023-12-23 7:04 ` kernel test robot
2023-12-25 2:53 ` [PATCH v4] " LeoLiu-oc
2023-12-26 0:54 ` kernel test robot
2023-12-26 1:04 ` kernel test robot [this message]
2023-12-26 7:49 ` kernel test robot
2023-12-27 3:58 ` [PATCH v5] " LeoLiu-oc
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=202312260844.FPx3YOsI-lkp@intel.com \
--to=lkp@intel.com \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=LeoLiu@zhaoxin.com \
--cc=TonyWWang@zhaoxin.com \
--cc=YunShen@zhaoxin.com \
--cc=ardb@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=herbert@gondor.apana.org.au \
--cc=jenny.zhang@starfivetech.com \
--cc=jiajie.ho@starfivetech.com \
--cc=l.stelmach@samsung.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@kaiser.cx \
--cc=mmyangfl@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olivia@selenic.com \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox