From: Paul Bolle <pebolle@tiscali.nl>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64: CONFIG_PARAVIRT_GUEST_ASM_CLOBBER_CHECK?
Date: Wed, 28 May 2014 22:46:27 +0000 [thread overview]
Message-ID: <1401317187.6186.36.camel@x220> (raw)
In-Reply-To: <1400748416.16832.7.camel@x220>
On Wed, 2014-05-28 at 22:34 +0000, Luck, Tony wrote:
> > Was this macro intended to be set through the kconfig tools? Or was it
> > perhaps intended to be set manually whenever one wanted to use it?
> > Either way, is that macro and the code currently hidden behind it still
> > needed?
>
> I think it may be moot. Xen support was ripped out in December last
> year by commit d52eefb47d4 ... so this even if this PARAVIRT piece
> one did something, it is all history now.
Should I draft an (untested, I'm afraid) patch to remove
CONFIG_PARAVIRT_GUEST_ASM_CLOBBER_CHECK and everything hidden behind it?
Or would you prefer to do that yourself?
Thanks,
Paul Bolle
prev parent reply other threads:[~2014-05-28 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 8:46 ia64: CONFIG_PARAVIRT_GUEST_ASM_CLOBBER_CHECK? Paul Bolle
2014-05-22 8:51 ` Paul Bolle
2014-05-28 22:34 ` Luck, Tony
2014-05-28 22:46 ` Paul Bolle [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=1401317187.6186.36.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-ia64@vger.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