From: kernel test robot <lkp@intel.com>
To: Lucas Poupeau <lucasp.linux@gmail.com>,
m32285159@gmail.com, richard.weiyang@gmail.com
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Lucas Poupeau <lucasp.linux@gmail.com>
Subject: Re: [PATCH] tools: include: add proper strscpy() declaration
Date: Mon, 11 May 2026 09:08:32 +0200 [thread overview]
Message-ID: <202605110823.9YvAiXAD-lkp@intel.com> (raw)
In-Reply-To: <20260506163452.53067-1-lucasp.linux@gmail.com>
Hi Lucas,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v7.1-rc3 next-20260508]
[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/Lucas-Poupeau/tools-include-add-proper-strscpy-declaration/20260511-103301
base: linus/master
patch link: https://lore.kernel.org/r/20260506163452.53067-1-lucasp.linux%40gmail.com
patch subject: [PATCH] tools: include: add proper strscpy() declaration
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260511/202605110823.9YvAiXAD-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260511/202605110823.9YvAiXAD-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/202605110823.9YvAiXAD-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from exec-cmd.c:3:
>> tools/include/linux/string.h:15:1: error: unknown type name 'ssize_t'; did you mean 'size_t'?
15 | ssize_t strscpy(char *dest, const char *src, size_t count);
| ^~~~~~~
| size_t
In file included from parse-options.c:3:
>> tools/include/linux/string.h:15:1: error: unknown type name 'ssize_t'; did you mean 'size_t'?
15 | ssize_t strscpy(char *dest, const char *src, size_t count);
| ^~~~~~~
| size_t
make[6]: *** [tools/build/Makefile.build:96: tools/objtool/libsubcmd/exec-cmd.o] Error 1
make[6]: *** [tools/build/Makefile.build:95: tools/objtool/libsubcmd/parse-options.o] Error 1
make[6]: Target '__build' not remade because of errors.
make[5]: *** [Makefile:78: tools/objtool/libsubcmd/libsubcmd-in.o] Error 2
make[5]: Target 'tools/objtool/libsubcmd/libsubcmd.a' not remade because of errors.
make[4]: *** [Makefile:135: tools/objtool/libsubcmd/libsubcmd.a] Error 2
make[4]: Target 'all' not remade because of errors.
make[3]: *** [Makefile:74: objtool] Error 2
make[2]: *** [Makefile:1557: tools/objtool] Error 2
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
vim +15 tools/include/linux/string.h
14
> 15 ssize_t strscpy(char *dest, const char *src, size_t count);
16
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-11 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 16:34 [PATCH] tools: include: add proper strscpy() declaration Lucas Poupeau
2026-05-06 16:47 ` Maxwell Doose
2026-05-07 2:42 ` Wei Yang
2026-05-07 3:11 ` Maxwell Doose
2026-05-11 7:08 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-04 21:23 Lucas Poupeau
2026-05-04 21:38 ` Maxwell Doose
2026-05-04 21:47 ` Maxwell Doose
2026-05-06 4:21 ` Maxwell Doose
2026-05-10 23:26 ` 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=202605110823.9YvAiXAD-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucasp.linux@gmail.com \
--cc=m32285159@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard.weiyang@gmail.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