All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Tang Yizhou <tangyizhou@huawei.com>,
	mingo@redhat.com, linux-doc@vger.kernel.org,
	zhengbin13@huawei.com, siyanteng@loongson.cn,
	siyanteng01@gmail.com, tangyeechou@gmail.com
Subject: Re: [PATCH] docs: scheduler: Convert schedutil.txt to ReST
Date: Sat, 12 Mar 2022 12:40:17 +0100	[thread overview]
Message-ID: <20220312114017.GA6235@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <87v8wk2ozc.fsf@meer.lwn.net>

On Fri, Mar 11, 2022 at 01:50:15PM -0700, Jonathan Corbet wrote:
> Tang Yizhou <tangyizhou@huawei.com> writes:
> 
> > All other scheduler documents have been converted to *.rst. Let's do
> > the same for schedutil.txt.
> >
> > Signed-off-by: Tang Yizhou <tangyizhou@huawei.com>
> > ---
> >  Documentation/scheduler/index.rst             |  1 +
> >  .../{schedutil.txt => schedutil.rst}          | 50 ++++++++++---------
> >  2 files changed, 28 insertions(+), 23 deletions(-)
> >  rename Documentation/scheduler/{schedutil.txt => schedutil.rst} (85%)
> 
> I would like to see this change made so that this document can be built
> with the rest of the kernel docs.  I will, however, defer to Peter and
> will not accept this change over his objections.

As I'm sure you're aware, I'd *love* to convert the whole lot to plain
text again :-)

People, throughout the ages, have been able to read plain text, I don't
see why it should be made more difficult than that.

      parent reply	other threads:[~2022-03-12 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  3:04 [PATCH] docs: scheduler: Convert schedutil.txt to ReST Tang Yizhou
2022-03-11 20:50 ` Jonathan Corbet
2022-03-12  6:29   ` Tang Yizhou
2022-03-12 11:40   ` Peter Zijlstra [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=20220312114017.GA6235@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.cn \
    --cc=tangyeechou@gmail.com \
    --cc=tangyizhou@huawei.com \
    --cc=zhengbin13@huawei.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 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.