From: Matthew Wilcox <willy@infradead.org>
To: "Ahmed S. Darwish" <darwi@linutronix.de>
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 21:05:15 +0000 [thread overview]
Message-ID: <aanwC228bGTa38LK@casper.infradead.org> (raw)
In-Reply-To: <20260305205023.361530-2-darwi@linutronix.de>
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?
> +.. 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.
> +With that in mind, any false real-time kernel configuration could cause a
incorrect rather than false, perhaps?
> +new maximum latency that shows up at the wrong time and is catastrophic
> +for the real-time system's latency.
next prev parent reply other threads:[~2026-03-05 21:05 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 [this message]
2026-03-05 21:45 ` Ahmed S. Darwish
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=aanwC228bGTa38LK@casper.infradead.org \
--to=willy@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=corbet@lwn.net \
--cc=darwi@linutronix.de \
--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 \
/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