From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Boris Kolpackov <boris@codesynthesis.com>
Subject: Re: [kbuild-all] Re: [masahiroy:kbuild 9/9] include/linux/byteorder/big_endian.h:8:2: error: #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN
Date: Wed, 9 Mar 2022 15:16:45 +0800 [thread overview]
Message-ID: <cf9f09bc-7fb3-2471-b347-51dd20b1109e@intel.com> (raw)
In-Reply-To: <CAK7LNASwGU=-KWfYbcHjEP=pyRvcwY5rmWk_X0a6wMz20s2Pqw@mail.gmail.com>
On 3/6/2022 12:19 AM, Masahiro Yamada wrote:
> On Thu, Mar 3, 2022 at 9:33 PM kernel test robot <lkp@intel.com> wrote:
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git kbuild
>> head: 55de8686df7ed2b5237867b130e30c728bbd9db4
>> commit: 55de8686df7ed2b5237867b130e30c728bbd9db4 [9/9] kconfig: change .config format to use =n instead of "is not set"
>> config: arc-randconfig-r005-20220302 (https://download.01.org/0day-ci/archive/20220303/202203032027.8qFpOWlq-lkp@intel.com/config)
>> compiler: arceb-elf-gcc (GCC) 11.2.0
>> 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
>> # https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?id=55de8686df7ed2b5237867b130e30c728bbd9db4
>> git remote add masahiroy https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
>> git fetch --no-tags masahiroy kbuild
>> git checkout 55de8686df7ed2b5237867b130e30c728bbd9db4
>> # save the config file to linux build tree
>> mkdir build_dir
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash lib/
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>> In file included from arch/arc/include/uapi/asm/byteorder.h:14,
>> from include/asm-generic/bitops/le.h:6,
>> from arch/arc/include/asm/bitops.h:192,
>> from include/linux/bitops.h:33,
>> from include/linux/log2.h:12,
>> from include/asm-generic/div64.h:55,
>> from ./arch/arc/include/generated/asm/div64.h:1,
>> from include/linux/math.h:5,
>> from include/linux/math64.h:6,
>> from include/linux/time.h:6,
>> from include/linux/stat.h:19,
>> from include/linux/module.h:13,
>> from lib/test_bitops.c:9:
>>>> include/linux/byteorder/big_endian.h:8:2: error: #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN [-Werror=cpp]
>> 8 | #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN
>> | ^~~~~~~
>> cc1: all warnings being treated as errors
>>
>>
>> vim +8 include/linux/byteorder/big_endian.h
>>
>> ^1da177e4c3f41 Linus Torvalds 2005-04-16 6
>> e9ef073a0796e4 Babu Moger 2017-09-08 7 #ifndef CONFIG_CPU_BIG_ENDIAN
>> e9ef073a0796e4 Babu Moger 2017-09-08 @8 #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN
>> e9ef073a0796e4 Babu Moger 2017-09-08 9 #endif
>> e9ef073a0796e4 Babu Moger 2017-09-08 10
>>
>> :::::: The code at line 8 was first introduced by commit
>> :::::: e9ef073a0796e46c24f037237291efe56fc28ad9 include: warn for inconsistent endian config definition
>>
>> :::::: TO: Babu Moger <babu.moger@oracle.com>
>> :::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
>>
>> ---
>> 0-DAY CI Kernel Test Service, Intel Corporation
>> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
>
> I cannot reproduce this.
>
> Maybe, this was a bug in make.cross
> (but already fixed??)
>
>
>
Hi Masahiro,
Sorry for the inconvenience, it's a false positive,
there's a bug in the CI was triggered by this commit.
Best Regards,
Rong Chen
prev parent reply other threads:[~2022-03-09 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 12:33 kernel test robot
2022-03-05 16:19 ` Masahiro Yamada
2022-03-09 7:16 ` Chen, Rong A [this message]
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=cf9f09bc-7fb3-2471-b347-51dd20b1109e@intel.com \
--to=rong.a.chen@intel.com \
--cc=boris@codesynthesis.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=masahiroy@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
all inboxes | Powered by JetHome®