Linux Documentation
 help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Clark Williams <clrkwllms@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-rt-devel@lists.linux.dev,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	John Ogness <john.ogness@linutronix.de>,
	Derek Barbosa <debarbos@redhat.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] Documentation: real-time: Add kernel configuration guide
Date: Thu, 5 Mar 2026 22:45:15 +0100	[thread overview]
Message-ID: <aan5a0QPKvwk7HF7@lx-t490> (raw)
In-Reply-To: <aanwC228bGTa38LK@casper.infradead.org>

Hi Matthew,

On Thu, 05 Mar 2026, Matthew Wilcox wrote:
>
> On Thu, Mar 05, 2026 at 09:50:12PM +0100, Ahmed S. Darwish wrote:
> > +==============================
> > +Real-Time Kernel configuration
> > +==============================
> > +
> > +.. Add a ToC so that all options can be seen in a glance
>
> Is this a useful comment?
>

I thought I'm the only one explicitly adding a ToC.  A quick grep shows
that to be false so I'll remove the comment.

> > +.. contents:: Table of Contents
> > +   :depth: 3
> > +   :local:
>
> [...]
>
> > +``CONFIG_CPU_FREQ``
> > +-------------------
> > +
> > +:Expectation: enabled
> > +:Severity: *high*
>
> Importance rather than Severity, perhaps?
>
> And high/medium/low rather than high/medium/info.
>

The info sections were meant to provide extra info on the kconfig options
w.r.t. PREEMPT_RT.  So, the CONFIG_DRM entry is not of low importance as
"Importance: low" would imply.  I'll think of something here.

> > +With that in mind, any false real-time kernel configuration could cause a
>
> incorrect rather than false, perhaps?
>

will do.

Thanks a lot,
Ahmed

  reply	other threads:[~2026-03-05 21:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 20:50 [PATCH v1 0/1] Documentation: Add real-time kernel configuration guide Ahmed S. Darwish
2026-03-05 20:50 ` [PATCH v1 1/1] Documentation: real-time: Add " Ahmed S. Darwish
2026-03-05 21:05   ` Matthew Wilcox
2026-03-05 21:45     ` Ahmed S. Darwish [this message]
2026-03-05 23:09     ` Steven Rostedt
2026-03-05 23:07   ` Steven Rostedt
2026-03-06 11:16     ` Ahmed S. Darwish

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=aan5a0QPKvwk7HF7@lx-t490 \
    --to=darwi@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --cc=corbet@lwn.net \
    --cc=debarbos@redhat.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=willy@infradead.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