From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.7] docs: Feature Levelling feature document
Date: Fri, 3 Jun 2016 16:36:25 +0100 [thread overview]
Message-ID: <5751A3F9.1070505@citrix.com> (raw)
In-Reply-To: <574EC73002000078000F0496@prv-mh.provo.novell.com>
On 01/06/16 10:29, Jan Beulich wrote:
>>>> On 31.05.16 at 19:05, <andrew.cooper3@citrix.com> wrote:
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
>
> with one spelling correction:
>
>> +# Overview
>> +
>> +On native hardware, a kernel will boot, detect features, typically optimise
>> +certain codepaths based on the available features, and expect the features to
>> +remain available until it shuts down.
>> +
>> +The same expectation exists for virtual machines, and it is up to the
>> +hypervisor/toolstack to fulfil this expectation for the lifetime of the
> fulfill
That is the American spelling. The English spelling does not have a
double l.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-03 15:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 17:05 [PATCH for-4.7] docs: Feature Levelling feature document Andrew Cooper
2016-06-01 9:29 ` Jan Beulich
2016-06-03 15:36 ` Andrew Cooper [this message]
2016-06-03 15:42 ` Jan Beulich
2016-06-03 15:53 ` Andrew Cooper
2016-06-01 9:41 ` Wei Liu
2016-06-01 10:25 ` Ian Jackson
2016-06-01 12:05 ` Andrew Cooper
2016-06-01 12:14 ` Ian Jackson
2016-06-01 13:11 ` Andrew Cooper
2016-06-03 14:59 ` [PATCH v2 " Ian Jackson
2016-06-03 15:35 ` Andrew Cooper
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=5751A3F9.1070505@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=wei.liu2@citrix.com \
--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).