From: kernel test robot <lkp@intel.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [frank-w-bpi-r2-4.14:7.2-main 209/209] drivers/net/phy/as21xx_1.9.2/as21xx_bbu_api/as21xx_debugfs.c:52:2: error: call to undeclared library function 'strncpy' with type 'char *(char *, const char *, __size_t)' (aka 'char *(char *, const char *, unsigned int)'); ISO C99 and later do not support...
Date: Tue, 01 Sep 2026 03:24:40 +0800 [thread overview]
Message-ID: <202609010356.FPlCP4le-lkp@intel.com> (raw)
tree: https://github.com/frank-w/BPI-R2-4.14 7.2-main
head: 63470c81335ce1106f6cebbf141b92a958a01e8a
commit: c5cd0ccfd13612a2ad02f2d734a6b35bf18b01bb [209/209] net: phy: as21xxx: update driver to v1.9.2
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260901/202609010356.FPlCP4le-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 316b0edee400b3ef72ed0a082dae9bd337ac01a0)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260901/202609010356.FPlCP4le-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/202609010356.FPlCP4le-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/net/phy/as21xx_1.9.2/as21xx_bbu_api/as21xx_debugfs.c:52:2: error: call to undeclared library function 'strncpy' with type 'char *(char *, const char *, __size_t)' (aka 'char *(char *, const char *, unsigned int)'); ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
52 | strncpy(buffer, input, sizeof(buffer));
| ^
drivers/net/phy/as21xx_1.9.2/as21xx_bbu_api/as21xx_debugfs.c:52:2: note: include the header <string.h> or explicitly provide a declaration for 'strncpy'
1 error generated.
vim +52 drivers/net/phy/as21xx_1.9.2/as21xx_bbu_api/as21xx_debugfs.c
38
39 /******************************************************************************
40 * Static Function
41 *****************************************************************************/
42 static int parse_cmd_args(const char *input, struct parsed_cmd *result, int max_args)
43 {
44 char buffer[MAX_BUF];
45 char *token, *ptr;
46 int count = 0;
47 size_t len;
48
49 if (!input || !result || max_args > MAX_ARGS)
50 return -EINVAL;
51
> 52 strncpy(buffer, input, sizeof(buffer));
53 buffer[sizeof(buffer) - 1] = '\0';
54
55 // clear '\n'
56 len = strlen(buffer);
57 if (len > 0 && buffer[len - 1] == '\n')
58 buffer[len - 1] = '\0';
59
60 ptr = buffer;
61
62 token = strsep(&ptr, " ");
63 while (token && *token == '\0')
64 token = strsep(&ptr, " ");
65
66 if (!token)
67 return -EINVAL;
68
69 strncpy(result->cmd, token, sizeof(result->cmd) - 1);
70 result->cmd[sizeof(result->cmd) - 1] = '\0';
71
72 while ((token = strsep(&ptr, " ")) != NULL && count < max_args) {
73 if (*token == '\0')
74 continue;
75
76 if (kstrtol(token, 0, &result->args[count]) != 0)
77 return -EINVAL;
78
79 count++;
80 }
81
82 result->argc = count;
83 return 0;
84 }
85
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-31 19:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202609010356.FPlCP4le-lkp@intel.com \
--to=lkp@intel.com \
--cc=frank-w@public-files.de \
--cc=oe-kbuild-all@lists.linux.dev \
/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.