From: Andi Kleen <ak@linux.intel.com>
To: kbuild test robot <lkp@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
kbuild-all@01.org, x86@kernel.org, linux-kernel@vger.kernel.org,
hpa@zytor.com
Subject: Re: [PATCH 2/5] x86/cpuid: Add generic table for cpuid dependencies
Date: Mon, 5 Jun 2017 15:50:45 -0700 [thread overview]
Message-ID: <20170605225045.GB30867@tassilo.jf.intel.com> (raw)
In-Reply-To: <201706041223.FXNUA0w6%fengguang.wu@intel.com>
> All errors (new ones prefixed by >>):
>
> >> ERROR: "clear_cpu_cap" [drivers/lguest/lg.ko] undefined!
It looks very broken what lguest does here. But ok, we can add a EXPORT_SYMBOL.
-Andi
next prev parent reply other threads:[~2017-06-05 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 22:22 [PATCH 1/5] x86/xsave: Move xsave initialization to after parsing early parameters Andi Kleen
2017-05-31 22:22 ` [PATCH 2/5] x86/cpuid: Add generic table for cpuid dependencies Andi Kleen
2017-06-04 4:10 ` kbuild test robot
2017-06-05 22:50 ` Andi Kleen [this message]
2017-05-31 22:22 ` [PATCH 3/5] x86/cpuid: Make clearcpuid an early param Andi Kleen
2017-05-31 22:22 ` [PATCH 4/5] x86/xsave: Make XSAVE check the base CPUID features before enabling Andi Kleen
2017-05-31 22:22 ` [PATCH 5/5] x86/xsave: Using generic CPUID clearing when disabling XSAVE Andi Kleen
2017-06-05 22:59 [PATCH 1/5] x86/xsave: Move xsave initialization to after parsing early parameters Andi Kleen
2017-06-05 22:59 ` [PATCH 2/5] x86/cpuid: Add generic table for cpuid dependencies Andi Kleen
2017-06-21 23:41 Support generic disabling of all XSAVE features Andi Kleen
2017-06-21 23:41 ` [PATCH 2/5] x86/cpuid: Add generic table for cpuid dependencies Andi Kleen
2017-06-22 9:28 ` Jonathan McDowell
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=20170605225045.GB30867@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=x86@kernel.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).