From: kernel test robot <lkp@intel.com>
To: Yangbo Lu <yangbo.lu@nxp.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: timestamping.c:328:56: warning: excess elements in struct initializer
Date: Tue, 19 Jul 2022 06:56:13 +0800 [thread overview]
Message-ID: <202207190632.Wf35yT5y-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 80e19f34c2887a8881084b7bb7480e9544d56b91
commit: 2214d7032479e50ff1fa7276e6efe1df08173fbf selftests/net: timestamping: support binding PHC
date: 1 year, 1 month 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 >>):
timestamping.c: In function 'main':
timestamping.c:328:16: error: variable 'so_timestamping_get' has initializer but incomplete type
328 | struct so_timestamping so_timestamping_get = { 0, -1 };
| ^~~~~~~~~~~~~~~
>> timestamping.c:328:56: warning: excess elements in struct initializer
328 | struct so_timestamping so_timestamping_get = { 0, -1 };
| ^
timestamping.c:328:56: note: (near initialization for 'so_timestamping_get')
timestamping.c:328:59: warning: excess elements in struct initializer
328 | struct so_timestamping so_timestamping_get = { 0, -1 };
| ^
timestamping.c:328:59: note: (near initialization for 'so_timestamping_get')
timestamping.c:328:32: error: storage size of 'so_timestamping_get' isn't known
328 | struct so_timestamping so_timestamping_get = { 0, -1 };
| ^~~~~~~~~~~~~~~~~~~
timestamping.c:329:16: error: variable 'so_timestamping' has initializer but incomplete type
329 | struct so_timestamping so_timestamping = { 0, -1 };
| ^~~~~~~~~~~~~~~
timestamping.c:329:52: warning: excess elements in struct initializer
329 | struct so_timestamping so_timestamping = { 0, -1 };
| ^
timestamping.c:329:52: note: (near initialization for 'so_timestamping')
timestamping.c:329:55: warning: excess elements in struct initializer
329 | struct so_timestamping so_timestamping = { 0, -1 };
| ^
timestamping.c:329:55: note: (near initialization for 'so_timestamping')
timestamping.c:329:32: error: storage size of 'so_timestamping' isn't known
329 | struct so_timestamping so_timestamping = { 0, -1 };
| ^~~~~~~~~~~~~~~
timestamping.c:378:50: error: 'SOF_TIMESTAMPING_BIND_PHC' undeclared (first use in this function); did you mean 'SOF_TIMESTAMPING_TX_ACK'?
378 | so_timestamping.flags |= SOF_TIMESTAMPING_BIND_PHC;
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| SOF_TIMESTAMPING_TX_ACK
timestamping.c:378:50: note: each undeclared identifier is reported only once for each function it appears in
>> timestamping.c:329:32: warning: unused variable 'so_timestamping' [-Wunused-variable]
329 | struct so_timestamping so_timestamping = { 0, -1 };
| ^~~~~~~~~~~~~~~
>> timestamping.c:328:32: warning: unused variable 'so_timestamping_get' [-Wunused-variable]
328 | struct so_timestamping so_timestamping_get = { 0, -1 };
| ^~~~~~~~~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-18 22:57 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=202207190632.Wf35yT5y-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangbo.lu@nxp.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
all inboxes | Powered by JetHome®