From: Jonathan Corbet <corbet@lwn.net>
To: Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: rdunlap@infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
laurent.pinchart@ideasonboard.com, hverkuil-cisco@xs4all.nl,
mchehab@kernel.org, kernel@collabora.com,
bob.beckett@collabora.com, nicolas.dufresne@collabora.com,
Sebastian Fricke <sebastian.fricke@collabora.com>
Subject: Re: [PATCH v3 0/2] Documentation: Debugging guide
Date: Fri, 22 Nov 2024 10:55:06 -0700 [thread overview]
Message-ID: <87ed332lxh.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241028-media_docs_improve_v3-v3-0-edf5c5b3746f@collabora.com>
Sebastian Fricke <sebastian.fricke@collabora.com> writes:
> The series 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.
OK, I don't see any real reason to send you around on this again; I've
just applied it, thanks.
jon
prev parent reply other threads:[~2024-11-22 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 7:03 Sebastian Fricke
2024-11-18 7:03 ` [PATCH v3 1/2] docs: Add debugging section to process Sebastian Fricke
2024-11-21 3:59 ` Randy Dunlap
2024-11-18 7:03 ` [PATCH v3 2/2] docs: Add debugging guide for the media subsystem Sebastian Fricke
2024-11-22 17:55 ` 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=87ed332lxh.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=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=rdunlap@infradead.org \
--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
all inboxes | Powered by JetHome®