From: kernel test robot <lkp@intel.com>
To: Erdem Aktas <erdemaktas@google.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Isaku Yamahata <isaku.yamahata@intel.com>,
Sean Christopherson <seanjc@google.com>,
Peter Gonda <pgonda@google.com>, Marc Orr <marcorr@google.com>,
Sagi Shahar <sagis@google.com>
Subject: [intel-tdx:kvm-upstream-workaround 207/314] include/x86_64/processor.h:761: warning: "__stringify_1" redefined
Date: Tue, 20 Sep 2022 06:30:48 +0800 [thread overview]
Message-ID: <202209200617.qET1i5ic-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 552dd80c48f67ca01bcdd10667e0c11efd375177
commit: 31055e94daecbccb36f6f4bfde26a583b2790a51 [207/314] KVM: selftest: Add helper functions to create TDX VMs
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce:
# https://github.com/intel/tdx/commit/31055e94daecbccb36f6f4bfde26a583b2790a51
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx kvm-upstream-workaround
git checkout 31055e94daecbccb36f6f4bfde26a583b2790a51
make O=/tmp/kselftest headers
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 error/warnings (new ones prefixed by >>):
In file included from lib/kvm_util.c:11:
>> include/x86_64/processor.h:761: warning: "__stringify_1" redefined
761 | #define __stringify_1(x) #x
|
In file included from include/x86_64/processor.h:18,
from lib/kvm_util.c:11:
../../../../tools/include/linux/stringify.h:10: note: this is the location of the previous definition
10 | #define __stringify_1(x...) #x
|
In file included from lib/kvm_util.c:11:
>> include/x86_64/processor.h:762: warning: "__stringify" redefined
762 | #define __stringify(x) __stringify_1(x)
|
In file included from include/x86_64/processor.h:18,
from lib/kvm_util.c:11:
../../../../tools/include/linux/stringify.h:11: note: this is the location of the previous definition
11 | #define __stringify(x...) __stringify_1(x)
|
lib/kvm_util.c: In function '____vm_create':
lib/kvm_util.c:191:20: error: 'type' undeclared (first use in this function)
191 | vm->type = type;
| ^~~~
lib/kvm_util.c:191:20: note: each undeclared identifier is reported only once for each function it appears in
--
In file included from lib/perf_test_util.c:9:
>> include/x86_64/processor.h:761: warning: "__stringify_1" redefined
761 | #define __stringify_1(x) #x
|
In file included from include/x86_64/processor.h:18,
from lib/perf_test_util.c:9:
../../../../tools/include/linux/stringify.h:10: note: this is the location of the previous definition
10 | #define __stringify_1(x...) #x
|
In file included from lib/perf_test_util.c:9:
>> include/x86_64/processor.h:762: warning: "__stringify" redefined
762 | #define __stringify(x) __stringify_1(x)
|
In file included from include/x86_64/processor.h:18,
from lib/perf_test_util.c:9:
../../../../tools/include/linux/stringify.h:11: note: this is the location of the previous definition
11 | #define __stringify(x...) __stringify_1(x)
|
--
In file included from lib/x86_64/processor.c:10:
>> lib/x86_64/tdx.h:6:10: fatal error: ../kvm_util_internal.h: No such file or directory
6 | #include "../kvm_util_internal.h"
| ^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-19 22:31 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=202209200617.qET1i5ic-lkp@intel.com \
--to=lkp@intel.com \
--cc=erdemaktas@google.com \
--cc=isaku.yamahata@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcorr@google.com \
--cc=pgonda@google.com \
--cc=sagis@google.com \
--cc=seanjc@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 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.