From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: xen-unstable build-failure: xg_cpuid_x86.c:99:42: error: ‘INIT_SPECIAL_FEATURES’ undeclared (first use in this function); did you mean ‘INIT_PV_MAX_FEATURES’?
Date: Tue, 8 Jun 2021 13:22:11 +0100 [thread overview]
Message-ID: <e296e60a-6199-ab80-5730-6c7e0cc96620@citrix.com> (raw)
In-Reply-To: <39b24aaf-a785-6dae-23fa-c9a787760565@eikelenboom.it>
On 08/06/2021 12:28, Sander Eikelenboom wrote:
> L.S.,
>
> I seem to be running into a build error with current xen-unstable.
Yeah - that's my fault.
https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=69e1472d21cf7e5cf0795ef38b99d00de78a910e
went a little too far, and shouldn't have dropped the changes in
gen-cpuid.py
It went unnoticed because the code below is obfuscated from grep, and
because the gitlab CI is currently blocked on earlier build failures
from the PV32 changes.
I'll do a patch when I've got a moment.
~Andrew
prev parent reply other threads:[~2021-06-08 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 11:28 xen-unstable build-failure: xg_cpuid_x86.c:99:42: error: ‘INIT_SPECIAL_FEATURES’ undeclared (first use in this function); did you mean ‘INIT_PV_MAX_FEATURES’? Sander Eikelenboom
2021-06-08 12:22 ` Andrew Cooper [this message]
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=e296e60a-6199-ab80-5730-6c7e0cc96620@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.org \
/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;
as well as URLs for NNTP newsgroup(s).