All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.5] docs/commandline: Fix formatting issues
Date: Wed, 19 Nov 2014 11:22:18 +0000	[thread overview]
Message-ID: <1416396138.29243.28.camel@citrix.com> (raw)
In-Reply-To: <1416395856-20849-1-git-send-email-andrew.cooper3@citrix.com>

On Wed, 2014-11-19 at 11:17 +0000, Andrew Cooper wrote:
> In both of these cases, markdown was interpreting the text as regular text,
> and reflowing it as a regular paragraph, leading to a single line as output.
> Reformat them as code blocks inside blockquote blocks, which causes them to
> take their precise whitespace layout.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Ian Campbell <Ian.Campbell@citrix.com>

> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
> CC: Wei Liu <wei.liu2@citrix.com>
> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> 
> ---
> 
> Konrad: this is a documentation fix, so requesting a 4.5 ack please.

FWIW IMHO documentation fixes in general should have a very low bar to
cross until very late in the release cycle...

> ---
>  docs/misc/xen-command-line.markdown |   38 +++++++++++++++++------------------
>  1 file changed, 19 insertions(+), 19 deletions(-)
> 
> diff --git a/docs/misc/xen-command-line.markdown b/docs/misc/xen-command-line.markdown
> index f054d4b..e3a5a15 100644
> --- a/docs/misc/xen-command-line.markdown
> +++ b/docs/misc/xen-command-line.markdown
> @@ -475,13 +475,13 @@ defaults of 1 and unlimited respectively are used instead.
>  
>  For example, with `dom0_max_vcpus=4-8`:
>  
> -     Number of
> -  PCPUs | Dom0 VCPUs
> -   2    |  4
> -   4    |  4
> -   6    |  6
> -   8    |  8
> -  10    |  8
> +>        Number of
> +>     PCPUs | Dom0 VCPUs
> +>      2    |  4
> +>      4    |  4
> +>      6    |  6
> +>      8    |  8
> +>     10    |  8
>  
>  ### dom0\_mem
>  > `= List of ( min:<size> | max:<size> | <size> )`
> @@ -684,18 +684,18 @@ supported only when compiled with XSM\_ENABLE=y on x86.
>  The specified value is a bit mask with the individual bits having the
>  following meaning:
>  
> -Bit  0 - debug level 0 (unused at present)
> -Bit  1 - debug level 1 (Control Register logging)
> -Bit  2 - debug level 2 (VMX logging of MSR restores when context switching)
> -Bit  3 - debug level 3 (unused at present)
> -Bit  4 - I/O operation logging
> -Bit  5 - vMMU logging
> -Bit  6 - vLAPIC general logging
> -Bit  7 - vLAPIC timer logging
> -Bit  8 - vLAPIC interrupt logging
> -Bit  9 - vIOAPIC logging
> -Bit 10 - hypercall logging
> -Bit 11 - MSR operation logging
> +>     Bit  0 - debug level 0 (unused at present)
> +>     Bit  1 - debug level 1 (Control Register logging)
> +>     Bit  2 - debug level 2 (VMX logging of MSR restores when context switching)
> +>     Bit  3 - debug level 3 (unused at present)
> +>     Bit  4 - I/O operation logging
> +>     Bit  5 - vMMU logging
> +>     Bit  6 - vLAPIC general logging
> +>     Bit  7 - vLAPIC timer logging
> +>     Bit  8 - vLAPIC interrupt logging
> +>     Bit  9 - vIOAPIC logging
> +>     Bit 10 - hypercall logging
> +>     Bit 11 - MSR operation logging
>  
>  Recognized in debug builds of the hypervisor only.
>  

  reply	other threads:[~2014-11-19 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 11:17 [PATCH for-4.5] docs/commandline: Fix formatting issues Andrew Cooper
2014-11-19 11:22 ` Ian Campbell [this message]
2014-11-19 21:21   ` Konrad Rzeszutek Wilk

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=1416396138.29243.28.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.