All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
	George.Dunlap@eu.citrix.com, ian.jackson@eu.citrix.com,
	tim@xen.org, ross.lagerwall@citrix.com, jbeulich@suse.com
Subject: Re: [PATCH v2 4/5] doc: correct feature-levelling.pandoc syntax
Date: Mon, 7 May 2018 11:26:52 +0100	[thread overview]
Message-ID: <17651b17-8a81-4c03-58fc-b3779c0963c7@citrix.com> (raw)
In-Reply-To: <20180507101608.797-5-jgross@suse.com>

On 07/05/18 11:16, Juergen Gross wrote:
> "make -C docs all" fails due to incorrect markdown syntax in
> feature-levelling.pandoc. Correct it.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>

What is trying to render this as markdown? It's pandoc, and the below
syntax is valid markdown (used extensively in xen-command-line.markdown)
so should be compatible in pandoc.

> ---
>  docs/features/feature-levelling.pandoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docs/features/feature-levelling.pandoc b/docs/features/feature-levelling.pandoc
> index ef77eb837d..4b2b6df151 100644
> --- a/docs/features/feature-levelling.pandoc
> +++ b/docs/features/feature-levelling.pandoc
> @@ -83,7 +83,7 @@ not trap, leaving Xen no direct ability to control the information returned.
>  
>  Xen-aware PV software can make use of the 'Forced Emulation Prefix'
>  
> -> `ud2a; .ascii 'xen'; cpuid`
> +        ud2a; .ascii 'xen'; cpuid
>  
>  which Xen recognises as a deliberate attempt to get the fully-controlled
>  `CPUID` information rather than the hardware-reported information.  This only


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-05-07 10:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 10:16 [PATCH v2 0/5] fix several issues in documentation Juergen Gross
2018-05-07 10:16 ` [PATCH v2 1/5] doc: add architecture qualifier to boot parameter entries Juergen Gross
2018-05-07 10:21   ` Andrew Cooper
2018-05-07 10:16 ` [PATCH v2 2/5] doc: add credit2_cap_period_ms boot parameter description Juergen Gross
2018-05-07 10:28   ` Andrew Cooper
2018-05-07 10:16 ` [PATCH v2 3/5] doc: correct livepatch.markdown syntax Juergen Gross
2018-05-07 10:23   ` Andrew Cooper
2018-05-07 10:30     ` Juergen Gross
2018-05-07 10:37       ` Andrew Cooper
2018-05-07 10:45         ` Juergen Gross
2018-05-07 10:16 ` [PATCH v2 4/5] doc: correct feature-levelling.pandoc syntax Juergen Gross
2018-05-07 10:26   ` Andrew Cooper [this message]
2018-05-07 10:34     ` Juergen Gross
2018-05-08 12:58   ` George Dunlap
2018-05-08 13:00     ` Andrew Cooper
2018-05-08 13:08       ` George Dunlap
2018-05-07 10:16 ` [PATCH v2 5/5] doc: correct intel_psr_cat_cdp.pandoc syntax Juergen Gross

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=17651b17-8a81-4c03-58fc-b3779c0963c7@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=ross.lagerwall@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 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.