From: Borislav Petkov <bp@alien8.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: mingo@kernel.org, dvlasenk@redhat.com, vkuznets@redhat.com,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
toshi.kani@hp.com, xen-devel@lists.xenproject.org,
luto@amacapital.net, mcgrof@suse.com, boris.ostrovsky@oracle.com,
jbeulich@suse.com, david.vrabel@citrix.com,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
brgerst@gmail.com, peterz@infradead.org, JGross@suse.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/asm] x86/mm/xen: Suppress hugetlbfs in PV guests
Date: Fri, 22 Apr 2016 20:16:43 +0200 [thread overview]
Message-ID: <20160422181643.GF15090@pd.tnic> (raw)
In-Reply-To: <571A6789.1040807@zytor.com>
On Fri, Apr 22, 2016 at 11:03:53AM -0700, H. Peter Anvin wrote:
> Please don't use the cpu_has_* macros anymore, they are going away soon.
>
> In this case it should be static_cpu_has(X86_FEATURE_PSE).
Ingo fixed this up while merging:
b2eafe890d4a ("Merge branch 'x86/urgent' into x86/asm, to fix semantic conflict")
The cpu_has_* things are gone now in tip! \o/
:-)
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-04-22 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 6:27 [PATCH] x86/xen: suppress hugetlbfs in PV guests Jan Beulich
2016-04-22 9:47 ` [tip:x86/asm] x86/mm/xen: Suppress " tip-bot for Jan Beulich
2016-04-22 18:03 ` H. Peter Anvin
2016-04-22 18:16 ` Borislav Petkov [this message]
2016-04-25 7:37 ` Jan Beulich
2016-04-25 7:52 ` Thomas Gleixner
2016-04-25 12:39 ` [Xen-devel] " David Vrabel
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=20160422181643.GF15090@pd.tnic \
--to=bp@alien8.de \
--cc=JGross@suse.com \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=brgerst@gmail.com \
--cc=david.vrabel@citrix.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=toshi.kani@hp.com \
--cc=vkuznets@redhat.com \
--cc=xen-devel@lists.xenproject.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