From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Cc: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] docs: correct descriptions of gnttab_max_{, maptrack}_frames
Date: Tue, 19 Jan 2016 14:22:00 +0000 [thread overview]
Message-ID: <1453213320.29930.53.camel@citrix.com> (raw)
In-Reply-To: <569E42FC.2060800@citrix.com>
On Tue, 2016-01-19 at 14:06 +0000, Andrew Cooper wrote:
> On 19/01/16 13:10, Ian Campbell wrote:
> > On Tue, 2016-01-19 at 06:06 -0700, Jan Beulich wrote:
> > > > > > On 19.01.16 at 12:56, <ian.campbell@citrix.com> wrote:
> > > > -Specify the maximum number of maptrack frames domain.
> > > > -The default value is 8 times **gnttab\_max\_frames**.
> > > > +> Default: `8 * gnttab_max_frames`
> > > No backslash escaping needed here?
> > No, not sure if the is ">" or the `` escaping them but the backslashes
> > appeared in the output HTML when I tried it.
> > > In any case,
> > > Acked-by: Jan Beulich <jbeulich@suse.com>
> > Thanks.
>
> Markdown is occasionally very lax, and occasionally very picky about its
> backslashes.
>
> I tend to insert them for piece of mind.
In this case they ended up in the output, which is wrong.
>
> Either way, Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
next prev parent reply other threads:[~2016-01-19 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 11:56 [PATCH] docs: correct descriptions of gnttab_max_{, maptrack}_frames Ian Campbell
2016-01-19 12:07 ` Ian Campbell
2016-01-19 13:06 ` Jan Beulich
2016-01-19 13:10 ` Ian Campbell
2016-01-19 14:06 ` Andrew Cooper
2016-01-19 14:22 ` Ian Campbell [this message]
2016-01-19 14:26 ` Andrew Cooper
2016-01-19 16:48 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2016-01-18 13:19 Ian Campbell
2016-01-18 13:48 ` Jan Beulich
2016-01-18 13:53 ` 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=1453213320.29930.53.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.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).