From: Julien Grall <julien.grall@arm.com>
To: Jan Beulich <JBeulich@suse.com>, Roger Pau Monne <roger.pau@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
IanJackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] docs: fix iommu_inclusive_mapping documentation
Date: Mon, 24 Apr 2017 12:34:15 +0100 [thread overview]
Message-ID: <b87a521c-8df0-cdc5-000c-1f35b19c1682@arm.com> (raw)
In-Reply-To: <58FA49000200007800153141@prv-mh.provo.novell.com>
Hi Jan,
On 21/04/17 17:01, Jan Beulich wrote:
>>>> On 21.04.17 at 16:36, <roger.pau@citrix.com> wrote:
>> --- a/docs/misc/xen-command-line.markdown
>> +++ b/docs/misc/xen-command-line.markdown
>> @@ -1083,7 +1083,7 @@ wait descriptor timed out', try increasing this value.
>> ### iommu\_inclusive\_mapping (VT-d)
>> > `= <boolean>`
>>
>> -> Default: `false`
>> +> Default: `true`
>>
>> Use this to work around firmware issues providing correct RMRR entries. Rather
>
> I think we should also take the opportunity and replace "correct" with
> "incorrect" above. Easily doable while committing. Any reason you
> didn't Cc Julien? A doc change like this should be quite fine for 4.9.
I am happy to see documentation change applied to staging without a
release-ack.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-04-24 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 14:36 [PATCH] docs: fix iommu_inclusive_mapping documentation Roger Pau Monne
2017-04-21 16:01 ` Jan Beulich
2017-04-21 16:13 ` Roger Pau Monne
2017-04-24 11:34 ` Julien Grall [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=b87a521c-8df0-cdc5-000c-1f35b19c1682@arm.com \
--to=julien.grall@arm.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.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;
as well as URLs for NNTP newsgroup(s).