From: kernel test robot <lkp@intel.com>
To: David Woodhouse <dwmw@amazon.co.uk>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [dwmw2:vmclock 22/23] ./usr/include/linux/vmclock.h:43:8: error: redefinition of 'vmclock_abi'
Date: Mon, 24 Jun 2024 04:54:32 +0800 [thread overview]
Message-ID: <202406240430.BsnyDimG-lkp@intel.com> (raw)
tree: git://git.infradead.org/users/dwmw2/linux vmclock
head: 82fa887512d4454c5688220793d2696a8ad00710
commit: c7b4ad8c548d23293f55a82d7147a4a6440f7c69 [22/23] ptp: Add vDSO-style vmclock support
config: x86_64-buildonly-randconfig-004-20240623 (https://download.01.org/0day-ci/archive/20240624/202406240430.BsnyDimG-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240624/202406240430.BsnyDimG-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/202406240430.BsnyDimG-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <built-in>:2:
>> ./usr/include/linux/vmclock.h:43:8: error: redefinition of 'vmclock_abi'
43 | struct vmclock_abi {
| ^
<built-in>:1:10: note: './usr/include/linux/vmclock.h' included multiple times, additional include site here
1 | #include "usr/include/linux/vmclock.h"
| ^
<built-in>:2:10: note: './usr/include/linux/vmclock.h' included multiple times, additional include site here
2 | #include "usr/include/linux/vmclock.h"
| ^
./usr/include/linux/vmclock.h:43:8: note: unguarded header; consider using #ifdef guards or #pragma once
43 | struct vmclock_abi {
| ^
1 error generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-23 20:54 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=202406240430.BsnyDimG-lkp@intel.com \
--to=lkp@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=llvm@lists.linux.dev \
--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.