From: kernel test robot <lkp@intel.com>
To: Coco Li <lixiaoyan@google.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: toeplitz.c:335:23: warning: excess elements in struct initializer
Date: Tue, 19 Jul 2022 08:07:44 +0800 [thread overview]
Message-ID: <202207190811.jZDv1ibc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 80e19f34c2887a8881084b7bb7480e9544d56b91
commit: 5ebfb4cc3048380b43506ffc71b9cf8b83128989 selftests/net: toeplitz test
date: 12 months ago
reproduce: make O=/tmp/kselftest -C tools/testing/selftests
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
toeplitz.c: In function 'create_ring':
toeplitz.c:334:16: error: variable 'args' has initializer but incomplete type
334 | struct fanout_args args = {
| ^~~~~~~~~~~
toeplitz.c:335:18: error: 'struct fanout_args' has no member named 'id'
335 | .id = 1,
| ^~
>> toeplitz.c:335:23: warning: excess elements in struct initializer
335 | .id = 1,
| ^
toeplitz.c:335:23: note: (near initialization for 'args')
toeplitz.c:336:18: error: 'struct fanout_args' has no member named 'type_flags'
336 | .type_flags = PACKET_FANOUT_CPU,
| ^~~~~~~~~~
In file included from toeplitz.c:33:
>> ../../../../usr/include/linux/if_packet.h:63:41: warning: excess elements in struct initializer
63 | #define PACKET_FANOUT_CPU 2
| ^
toeplitz.c:336:31: note: in expansion of macro 'PACKET_FANOUT_CPU'
336 | .type_flags = PACKET_FANOUT_CPU,
| ^~~~~~~~~~~~~~~~~
../../../../usr/include/linux/if_packet.h:63:41: note: (near initialization for 'args')
63 | #define PACKET_FANOUT_CPU 2
| ^
toeplitz.c:336:31: note: in expansion of macro 'PACKET_FANOUT_CPU'
336 | .type_flags = PACKET_FANOUT_CPU,
| ^~~~~~~~~~~~~~~~~
toeplitz.c:337:18: error: 'struct fanout_args' has no member named 'max_num_members'
337 | .max_num_members = RSS_MAX_CPUS
| ^~~~~~~~~~~~~~~
toeplitz.c:64:22: warning: excess elements in struct initializer
64 | #define RSS_MAX_CPUS (1 << 16) /* real constraint is PACKET_FANOUT_MAX */
| ^
toeplitz.c:337:36: note: in expansion of macro 'RSS_MAX_CPUS'
337 | .max_num_members = RSS_MAX_CPUS
| ^~~~~~~~~~~~
toeplitz.c:64:22: note: (near initialization for 'args')
64 | #define RSS_MAX_CPUS (1 << 16) /* real constraint is PACKET_FANOUT_MAX */
| ^
toeplitz.c:337:36: note: in expansion of macro 'RSS_MAX_CPUS'
337 | .max_num_members = RSS_MAX_CPUS
| ^~~~~~~~~~~~
toeplitz.c:334:28: error: storage size of 'args' isn't known
334 | struct fanout_args args = {
| ^~~~
>> toeplitz.c:334:28: warning: unused variable 'args' [-Wunused-variable]
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-19 0:08 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=202207190811.jZDv1ibc-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=willemb@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