From: kernel test robot <lkp@intel.com>
To: tanzirh@google.com, Kees Cook <keescook@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev, Andy Shevchenko <andy@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
Nick DeSaulniers <nnn@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
llvm@lists.linux.dev, Tanzir Hasan <tanzirh@google.com>
Subject: Re: [PATCH] lib/string: shrink lib/string.i via IWYU
Date: Wed, 6 Dec 2023 15:10:46 +0800 [thread overview]
Message-ID: <202312061429.BJ7GrHnt-lkp@intel.com> (raw)
In-Reply-To: <20231205-libstringheader-v1-1-7f9c573053a7@gmail.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on 33cc938e65a98f1d29d0a18403dbbee050dcad9a]
url: https://github.com/intel-lab-lkp/linux/commits/tanzirh-google-com/lib-string-shrink-lib-string-i-via-IWYU/20231206-050121
base: 33cc938e65a98f1d29d0a18403dbbee050dcad9a
patch link: https://lore.kernel.org/r/20231205-libstringheader-v1-1-7f9c573053a7%40gmail.com
patch subject: [PATCH] lib/string: shrink lib/string.i via IWYU
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20231206/202312061429.BJ7GrHnt-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231206/202312061429.BJ7GrHnt-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/202312061429.BJ7GrHnt-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from lib/string.c:29:
lib/string.c: In function 'strscpy':
>> arch/sh/include/asm/word-at-a-time.h:15:36: error: implicit declaration of function 'REPEAT_BYTE' [-Werror=implicit-function-declaration]
15 | #define WORD_AT_A_TIME_CONSTANTS { REPEAT_BYTE(0x01), REPEAT_BYTE(0x80) }
| ^~~~~~~~~~~
lib/string.c:124:49: note: in expansion of macro 'WORD_AT_A_TIME_CONSTANTS'
124 | const struct word_at_a_time constants = WORD_AT_A_TIME_CONSTANTS;
| ^~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/REPEAT_BYTE +15 arch/sh/include/asm/word-at-a-time.h
cba8df4be3bdf1 Paul Mundt 2012-06-04 14
cba8df4be3bdf1 Paul Mundt 2012-06-04 @15 #define WORD_AT_A_TIME_CONSTANTS { REPEAT_BYTE(0x01), REPEAT_BYTE(0x80) }
cba8df4be3bdf1 Paul Mundt 2012-06-04 16
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2023-12-06 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231205-libstringheader-v1-1-7f9c573053a7@gmail.com>
2023-12-06 7:10 ` kernel test robot [this message]
2023-12-07 12:55 ` [PATCH] lib/string: shrink lib/string.i via IWYU Andy Shevchenko
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=202312061429.BJ7GrHnt-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andy@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=nnn@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tanzirh@google.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).