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, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, leoliu@zhaoxin.com,
CobeChen@zhaoxin.com, YunShen@zhaoxin.com, TonyWWang@zhaoxin.com,
leoliu-oc <leoliu-oc@zhaoxin.com>
Subject: Re: [PATCH v2 2/2] hwrng: add Zhaoxin HW RNG driver
Date: Mon, 31 Jul 2023 18:22:12 +0800 [thread overview]
Message-ID: <202307311838.VQTSuKH4-lkp@intel.com> (raw)
In-Reply-To: <20230731084515.2057375-3-LeoLiu-oc@zhaoxin.com>
Hi LeoLiu-oc,
kernel test robot noticed the following build warnings:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus herbert-cryptodev-2.6/master linus/master v6.5-rc4 next-20230731]
[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-via-rng-convert-to-x86_cpu_id-probing/20230731-164950
base: char-misc/char-misc-testing
patch link: https://lore.kernel.org/r/20230731084515.2057375-3-LeoLiu-oc%40zhaoxin.com
patch subject: [PATCH v2 2/2] hwrng: add Zhaoxin HW RNG driver
config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20230731/202307311838.VQTSuKH4-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230731/202307311838.VQTSuKH4-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/202307311838.VQTSuKH4-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/loongarch/include/asm/inst.h:10,
from arch/loongarch/include/asm/uprobes.h:5,
from include/linux/uprobes.h:49,
from include/linux/mm_types.h:16,
from include/linux/buildid.h:5,
from include/linux/module.h:14,
from drivers/char/hw_random/zhaoxin-rng.c:10:
>> arch/loongarch/include/asm/asm.h:35: warning: "STACK_ALIGN" redefined
35 | #define STACK_ALIGN ~(0xf)
|
In file included from drivers/char/hw_random/zhaoxin-rng.c:9:
include/crypto/padlock.h:19: note: this is the location of the previous definition
19 | #define STACK_ALIGN 16
|
drivers/char/hw_random/zhaoxin-rng.c:16:10: fatal error: asm/cpu_device_id.h: No such file or directory
16 | #include <asm/cpu_device_id.h>
| ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +/STACK_ALIGN +35 arch/loongarch/include/asm/asm.h
b738c106f7355e Huacai Chen 2022-05-31 31
b738c106f7355e Huacai Chen 2022-05-31 32 /*
b738c106f7355e Huacai Chen 2022-05-31 33 * Stack alignment
b738c106f7355e Huacai Chen 2022-05-31 34 */
b738c106f7355e Huacai Chen 2022-05-31 @35 #define STACK_ALIGN ~(0xf)
b738c106f7355e Huacai Chen 2022-05-31 36
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-07-31 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 8:45 [PATCH v2 0/2] Add Zhaoxin HW RNG support LeoLiu-oc
2023-07-31 8:45 ` [PATCH v2 1/2] hwrng: via-rng: convert to x86_cpu_id probing LeoLiu-oc
2023-07-31 8:45 ` [PATCH v2 2/2] hwrng: add Zhaoxin HW RNG driver LeoLiu-oc
2023-07-31 10:22 ` kernel test robot [this message]
2023-07-31 12:04 ` kernel test robot
2023-07-31 12:04 ` kernel test robot
2023-07-31 13:06 ` 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=202307311838.VQTSuKH4-lkp@intel.com \
--to=lkp@intel.com \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=TonyWWang@zhaoxin.com \
--cc=YunShen@zhaoxin.com \
--cc=conor.dooley@microchip.com \
--cc=herbert@gondor.apana.org.au \
--cc=jenny.zhang@starfivetech.com \
--cc=jiajie.ho@starfivetech.com \
--cc=leoliu@zhaoxin.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 \
/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;
as well as URLs for NNTP newsgroup(s).