From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>, Eddie Dong <eddie.dong@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: A simple clean up of __get_instruction_length & __update_guest_eip
Date: Wed, 15 Sep 2010 16:38:23 +0100 [thread overview]
Message-ID: <C8B6A6FF.23109%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C91018C02000078000165DD@vpn.id2.novell.com>
On 15/09/2010 16:25, "Jan Beulich" <JBeulich@novell.com> wrote:
> Is it really a good idea to remove all these "Safe: ..." comments?
> Without them, I think it'll be much easier to not remember that
> this cannot be done everywhere and hence to add an inappropriate
> call to this function.
I meant to check they were kept, and then forgot and applied it anyway. I'll
add them back in.
--Keir
prev parent reply other threads:[~2010-09-15 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 14:34 A simple clean up of __get_instruction_length & __update_guest_eip Dong, Eddie
2010-09-15 15:25 ` Jan Beulich
2010-09-15 15:38 ` Keir Fraser [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=C8B6A6FF.23109%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=eddie.dong@intel.com \
--cc=xen-devel@lists.xensource.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 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).