From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev, Boqun Feng <boqun.feng@gmail.com>,
Clark Williams <clrkwllms@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
John Ogness <john.ogness@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Valentin Schneider <vschneid@redhat.com>,
Waiman Long <longman@redhat.com>, Will Deacon <will@kernel.org>
Subject: Re: [PATCH 3/3] Documentation: Add real-time
Date: Fri, 15 Aug 2025 11:20:19 +0200 [thread overview]
Message-ID: <20250815092019.EAd9FdNN@linutronix.de> (raw)
In-Reply-To: <87v7ntdwp5.fsf@trenco.lwn.net>
On 2025-07-15 14:29:42 [-0600], Jonathan Corbet wrote:
> So overall it looks good, but I do have one overriding question:
>
> - Who is the audience for this documentation?
>
> I think it's an important question to ask, because something this easily
> becomes an unorganized pile of stuff that somebody thought should be
> written down somewhere - better than nothing, but hard for readers to
> use effectively.
>
> A good first step would be to supply a paragraph or two in the new
> Documentation/real-time/index.rst describing the nature of the
> documentation and who it is intended for.
The main audience are kernel developers.
> Then ... think about whether a new top-level directory under
> Documentation makes sense. I've been working for years to reduce those,
> so I tend to push back a little when new ones show up.
>
> - Is this documentation for kernel developers in general, with the idea
> of maybe helping them to not break PREEMPT_RT so often? Then perhaps
> documentation with that focus under core-api/ makes sense.
>
> - Is it, instead, intended as overall design documentation? We don't
> really have a good place for that now, maybe we need a new design/
> book to gather such material.
>
> See what I'm getting at? I'm not saying that these docs *have* to go
> somewhere else, but I do think it's worth thinking about.
While thinking about it I moved it to core-api. There might some user
bits which in terms of setup which might fit under admin-guide.
> Thanks,
>
> jon
Sebastian
prev parent reply other threads:[~2025-08-15 9:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 14:41 [PATCH 0/3] Documentation: Add real-time bits Sebastian Andrzej Siewior
2025-07-15 14:41 ` [PATCH 1/3] Documentation: seqlock: Add a reference label and license Sebastian Andrzej Siewior
2025-07-15 14:48 ` Jonathan Corbet
2025-07-15 14:53 ` Sebastian Andrzej Siewior
2025-07-15 14:41 ` [PATCH 2/3] Documentation: locking: Add local_lock_nested_bh() to locktypes Sebastian Andrzej Siewior
2025-07-15 20:10 ` Jonathan Corbet
2025-08-14 8:40 ` Sebastian Andrzej Siewior
2025-07-15 14:41 ` [PATCH 3/3] Documentation: Add real-time Sebastian Andrzej Siewior
2025-07-15 14:50 ` Jonathan Corbet
2025-07-15 14:55 ` Sebastian Andrzej Siewior
2025-07-15 20:29 ` Jonathan Corbet
2025-08-15 9:20 ` Sebastian Andrzej Siewior [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=20250815092019.EAd9FdNN@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=clrkwllms@kernel.org \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--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=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).