From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Allison Randal <allison@lohutok.net>
Subject: [gregkh-spdx:spdx-linus 16/26] arch/x86/crypto/crc32-pclmul_asm.S:2: Error: junk at end of line, first unrecognized character is `*'
Date: Sat, 11 Jun 2022 09:56:51 +0800 [thread overview]
Message-ID: <202206110936.UIMGLIoN-lkp@intel.com> (raw)
Hi Thomas,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/spdx.git spdx-linus
head: ce3f3ccc90b8207946a4eea45c4bd539e35cbe2c
commit: 2eb72d6696c685369fca7cd63cb4b76d1be099e0 [16/26] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_179.RULE
config: i386-debian-10.3-kselftests (https://download.01.org/0day-ci/archive/20220611/202206110936.UIMGLIoN-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/spdx.git/commit/?id=2eb72d6696c685369fca7cd63cb4b76d1be099e0
git remote add gregkh-spdx https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/spdx.git
git fetch --no-tags gregkh-spdx spdx-linus
git checkout 2eb72d6696c685369fca7cd63cb4b76d1be099e0
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash arch/x86/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/x86/crypto/crc32-pclmul_asm.S: Assembler messages:
>> arch/x86/crypto/crc32-pclmul_asm.S:2: Error: junk at end of line, first unrecognized character is `*'
vim +2 arch/x86/crypto/crc32-pclmul_asm.S
78c37d191dd689 Alexander Boyko 2013-01-10 @2 */
78c37d191dd689 Alexander Boyko 2013-01-10 3
:::::: The code at line 2 was first introduced by commit
:::::: 78c37d191dd6899d8c219fee597a17d6e3c5d288 crypto: crc32 - add crc32 pclmulqdq implementation and wrappers for table implementation
:::::: TO: Alexander Boyko <alexander_boyko@xyratex.com>
:::::: CC: Herbert Xu <herbert@gondor.apana.org.au>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-06-11 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 1:56 kernel test robot [this message]
2022-06-13 7:38 ` [PATCH] x86/crypto: Remove stray comment terminator Thomas Gleixner
2022-06-13 7:38 ` Thomas Gleixner
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=202206110936.UIMGLIoN-lkp@intel.com \
--to=lkp@intel.com \
--cc=allison@lohutok.net \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.