From: Randy Dunlap <rdunlap@infradead.org>
To: linux-debuggers@vger.kernel.org
Subject: dedicated kernel docum. directory for Debug
Date: Sat, 30 Nov 2024 00:06:32 -0800 [thread overview]
Message-ID: <63e50929-6591-4931-8db0-4877b0899425@infradead.org> (raw)
Hi,
There is now a dedicated kernel debuggers/debugging sub-directory
(just added during the v6.12++ merge window):
Documentation/process/debugging/.
There is currently only a little debugger/debugging documentation there
but if any of you know something that should be added there, please don't
hesitate to do so. (speaking for myself only)
thanks.
--
~Randy
reply other threads:[~2024-11-30 8:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=63e50929-6591-4931-8db0-4877b0899425@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-debuggers@vger.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