From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, tim@xen.org,
ross.lagerwall@citrix.com, jbeulich@suse.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 1/2] doc: correct livepatch.markdown syntax
Date: Fri, 11 May 2018 13:56:22 -0400 [thread overview]
Message-ID: <20180511175622.GA10866@char.us.oracle.com> (raw)
In-Reply-To: <8c20fe4f-ec3b-678d-fb16-bef1929926a5@citrix.com>
On Tue, May 08, 2018 at 11:51:47AM +0100, George Dunlap wrote:
> On 05/08/2018 07:47 AM, Juergen Gross wrote:
> > "make -C docs all" fails due to incorrect markdown syntax in
> > livepatch.markdown. Correct it.
> >
> > Signed-off-by: Juergen Gross <jgross@suse.com>
> > Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> Git complains of trailing whitespace:
>
> Importing patch "doc-correct-livepatch-markdown" ... <stdin>:69:
> trailing whitespace.
>
> <stdin>:72: trailing whitespace.
>
> <stdin>:98: trailing whitespace.
>
> <stdin>:232: trailing whitespace.
>
> <stdin>:238: trailing whitespace.
That is on purpose. That is you need those two spaces at the end to force
it to stay in 'code' mode.
>
> Checking patch docs/misc/livepatch.markdown...
> Applied patch docs/misc/livepatch.markdown cleanly.
> warning: squelched 13 whitespace errors
> warning: 18 lines add whitespace errors.
>
>
> > ---
> > docs/misc/livepatch.markdown | 590 ++++++++++++++++++++-----------------------
> > 1 file changed, 273 insertions(+), 317 deletions(-)
> >
> > diff --git a/docs/misc/livepatch.markdown b/docs/misc/livepatch.markdown
> > index 54a6b850cb..a4de44472a 100644
> > --- a/docs/misc/livepatch.markdown
> > +++ b/docs/misc/livepatch.markdown
> > @@ -89,33 +89,27 @@ As example we will assume the hypervisor does not have XSA-132 (see
> > 4ff3449f0e9d175ceb9551d3f2aecb59273f639d) and we would like to binary patch
> > the hypervisor with it. The original code looks as so:
> >
> > -<pre>
> > - 48 89 e0 mov %rsp,%rax
> > - 48 25 00 80 ff ff and $0xffffffffffff8000,%rax
> > -</pre>
> > + 48 89 e0 mov %rsp,%rax
> > + 48 25 00 80 ff ff and $0xffffffffffff8000,%rax
> >
> > while the new patched hypervisor would be:
> >
> > -<pre>
> > - 48 c7 45 b8 00 00 00 00 movq $0x0,-0x48(%rbp)
> > - 48 c7 45 c0 00 00 00 00 movq $0x0,-0x40(%rbp)
> > - 48 c7 45 c8 00 00 00 00 movq $0x0,-0x38(%rbp)
> > - 48 89 e0 mov %rsp,%rax
> > - 48 25 00 80 ff ff and $0xffffffffffff8000,%rax
> > -</pre>
> > + 48 c7 45 b8 00 00 00 00 movq $0x0,-0x48(%rbp)
> > + 48 c7 45 c0 00 00 00 00 movq $0x0,-0x40(%rbp)
> > + 48 c7 45 c8 00 00 00 00 movq $0x0,-0x38(%rbp)
> > + 48 89 e0 mov %rsp,%rax
> > + 48 25 00 80 ff ff and $0xffffffffffff8000,%rax
> >
> > -This is inside the arch_do_domctl. This new change adds 21 extra
> > +This is inside the arch\_do\_domctl. This new change adds 21 extra
>
> It seems like nearly all of these would be better served by making them
> code blocks ( `arch_do_domctl`). It is:
> * easier to read in text format (one of the main points of markdown),
> * fewer characters to type,
> * looks better rendered into html or pdf, and
> * doesn't require < > tags for < and >.
>
> -George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-05-11 17:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 6:47 [PATCH v3 0/2] fix several issues in documentation Juergen Gross
2018-05-08 6:47 ` [PATCH v3 1/2] doc: correct livepatch.markdown syntax Juergen Gross
2018-05-08 9:55 ` [PATCH v3.5 " Andrew Cooper
2018-05-18 17:35 ` [PATCH for-4.11 " Andrew Cooper
2018-05-21 8:56 ` Wei Liu
2018-05-08 10:51 ` [PATCH v3 " George Dunlap
2018-05-11 17:56 ` Konrad Rzeszutek Wilk [this message]
2018-05-11 17:58 ` Andrew Cooper
2018-05-08 6:47 ` [PATCH v3 2/2] doc: correct intel_psr_cat_cdp.pandoc syntax Juergen Gross
2018-05-08 12:56 ` George Dunlap
2018-05-08 13:06 ` Juergen Gross
2018-07-10 13:24 ` Juergen Gross
2018-07-10 14:09 ` Wei Liu
2018-05-08 9:25 ` [PATCH v3 0/2] fix several issues in documentation George Dunlap
2018-05-08 9:32 ` Juergen Gross
2018-05-08 13:08 ` Ian Jackson
2018-05-08 13:10 ` George Dunlap
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=20180511175622.GA10866@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@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 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).