From: Jonathan Corbet <corbet@lwn.net>
To: Hui Su <sh_def@163.com>
Cc: dsterba@suse.com, mchehab+huawei@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/cpu-load: format the example code.
Date: Wed, 21 Oct 2020 15:08:29 -0600 [thread overview]
Message-ID: <20201021150829.125bf59e@lwn.net> (raw)
In-Reply-To: <20201018170557.GA7670@rlk>
On Mon, 19 Oct 2020 01:05:57 +0800
Hui Su <sh_def@163.com> wrote:
> format the example code.
>
> Signed-off-by: Hui Su <sh_def@163.com>
> ---
> Documentation/admin-guide/cpu-load.rst | 63 ++++++++++++++------------
> 1 file changed, 33 insertions(+), 30 deletions(-)
Hmm...this document wasn't always that way; it looks like maybe the code
got mangled during the RST conversion.
I question the value of this document in general...but as long as we have
it the code might as well look right, so I've applied this, thanks.
jon
prev parent reply other threads:[~2020-10-21 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 17:05 [PATCH] docs/cpu-load: format the example code Hui Su
2020-10-21 21:08 ` Jonathan Corbet [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=20201021150829.125bf59e@lwn.net \
--to=corbet@lwn.net \
--cc=dsterba@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=sh_def@163.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).