From: Jonathan Corbet <corbet@lwn.net>
To: "Ahmed S. Darwish" <darwi@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-rt-devel@lists.linux.dev
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
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,
"Ahmed S. Darwish" <darwi@linutronix.de>
Subject: Re: [PATCH v6 1/1] Documentation: real-time: Add kernel configuration guide
Date: Wed, 05 Aug 2026 13:42:13 -0600 [thread overview]
Message-ID: <87pkzwnylm.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260804141541.747704-2-darwi@linutronix.de>
"Ahmed S. Darwish" <darwi@linutronix.de> writes:
> Add a configuration guide for real-time kernels.
>
> List all Kconfig options that are recommended to be either enabled or
> disabled. Explicitly add a table of contents at the top of the document,
> so that all the options can be seen in a glance.
>
> Whenever appropriate, link to other kernel guides; e.g. cpuidle, cpufreq,
> power management, workqueues, and no_hz.
>
> Add a summary at the end of the document warning users that there is no
> "one size fits all solution" for configuring a real-time system.
>
> Signed-off-by: Ahmed S. Darwish <darwi@linutronix.de>
> ---
> Documentation/core-api/real-time/index.rst | 1 +
> .../real-time/kernel-configuration.rst | 307 ++++++++++++++++++
> 2 files changed, 308 insertions(+)
> create mode 100644 Documentation/core-api/real-time/kernel-configuration.rst
So would you like me to pick this up in the docs tree, or did you have
another path in mind?
Thanks,
jon
next prev parent reply other threads:[~2026-08-05 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 14:15 [PATCH v6 0/1] Documentation: Add real-time kernel configuration guide Ahmed S. Darwish
2026-08-04 14:15 ` [PATCH v6 1/1] Documentation: real-time: Add " Ahmed S. Darwish
2026-08-05 19:42 ` Jonathan Corbet [this message]
2026-08-06 8:02 ` 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=87pkzwnylm.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--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=rafael@kernel.org \
--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