From: Keir Fraser <keir@xen.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
"Justin T. Gibbs" <justing@spectralogic.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Improve documentation of the blkif interface
Date: Thu, 01 Mar 2012 16:25:18 +0000 [thread overview]
Message-ID: <CB75536E.3AAA2%keir@xen.org> (raw)
In-Reply-To: <20303.38548.120068.759929@mariner.uk.xensource.com>
On 01/03/2012 15:32, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
> Justin T. Gibbs writes ("[Xen-devel] [PATCH] Improve documentation of the
> blkif interface"):
>> o Fix typo "discard-aligment" -> "discard-alignment"
>> o Fix typo "unamp" -> "unmap"
>> o Fix typo "formated" -> "formatted"
>> o Clarify the text for "params".
>> o Clarify the text for "sector-size".
>>
>> No functional changes.
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
>
> Keir, is it OK in general for me to commit these kind of docs changes
> to the xen headers (provided they strictly are docs changes and don't
> mess with the #defines etc.) ?
Yep, fine with me.
-- Keir
> Thanks,
> Ian.
prev parent reply other threads:[~2012-03-01 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 22:08 [PATCH] Improve documentation of the blkif interface Justin T. Gibbs
2012-03-01 15:32 ` Ian Jackson
2012-03-01 16:25 ` 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=CB75536E.3AAA2%keir@xen.org \
--to=keir@xen.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=justing@spectralogic.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).