From: Jonathan Corbet <corbet@lwn.net>
To: Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
hverkuil-cisco@xs4all.nl, mauro.chehab@linux.intel.com,
kernel@collabora.com, bob.beckett@collabora.com,
nicolas.dufresne@collabora.com,
Sebastian Fricke <sebastian.fricke@collabora.com>
Subject: Re: [PATCH RFC v2 0/3] Documentation: Debugging guide
Date: Thu, 24 Oct 2024 16:01:22 -0600 [thread overview]
Message-ID: <87frol2ma5.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240529-b4-media_docs_improve-v2-0-66318b2da726@collabora.com>
Sebastian Fricke <sebastian.fricke@collabora.com> writes:
> The RFC contains:
> - a general debugging guide split into debugging for driver developers and
> debugging from userspace
> - a new summary page for all media related documentation. This is inspired by
> other subsystems, which first of all allows a user to find the subsystem
> under the subsystems page and secondly eases general navigation through the
> documentation that is sprinkled onto multiple places.
> - a guide on how to debug code in the media subsystem, which points to the
> parts of the general documentation and adds own routines.
I've just begun to take a look at this, apologies for taking so long.
Overall:
- I have been trying to reduce the number of top-level directories under
Documentation/, and this adds two more. Can we avoid that? Let's
start in that direction by putting your debugging guide inside
Documentation/process, please.
- If we *must* create a separate "media" directory, please make it
devices/media. My plan is to move most of the device-specific
documentation under Documentation/devices, making it match the source
layout; I just haven't summoned up the energy to start the slog of
actually doing it.
But it would be nice to avoid that altogether here. If we create
Documentation/process/debugging/, it should be able to hold both your
general and media-specific guides, and perhaps other
subsystem-specific guides could eventually land there as well.
- Please adhere to the 80-column limit for written text. It really does
make a difference for people reading it.
Thanks,
jon
prev parent reply other threads:[~2024-10-24 22:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 8:45 [PATCH RFC v2 0/3] Documentation: Debugging guide Sebastian Fricke
2024-09-24 8:45 ` [PATCH RFC v2 1/3] docs: media: Create separate documentation folder for media Sebastian Fricke
2024-09-24 8:45 ` [PATCH RFC v2 2/3] docs: Add guides section for debugging Sebastian Fricke
2024-09-25 8:01 ` Bagas Sanjaya
2024-10-03 23:06 ` Steve Cho
2024-10-04 10:12 ` Sebastian Fricke
2024-10-04 23:30 ` Steve Cho
2024-10-24 22:20 ` Jonathan Corbet
2024-09-24 8:45 ` [PATCH RFC v2 3/3] docs: media: Debugging guide for the media subsystem Sebastian Fricke
2024-10-03 22:32 ` Steve Cho
2024-10-14 17:42 ` Daniel Almeida
2024-10-23 11:43 ` Hans Verkuil
2024-10-23 12:29 ` Laurent Pinchart
2024-10-23 12:37 ` Hans Verkuil
2024-10-23 13:04 ` Dave Stevenson
2024-10-22 15:23 ` [PATCH RFC v2 0/3] Documentation: Debugging guide Sebastian Fricke
2024-10-23 6:57 ` Bagas Sanjaya
2024-10-24 22:01 ` Jonathan Corbet [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=87frol2ma5.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bob.beckett@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mauro.chehab@linux.intel.com \
--cc=nicolas.dufresne@collabora.com \
--cc=sebastian.fricke@collabora.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 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).