From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
anish kumar <yesanishhere@gmail.com>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-sound@vger.kernel.org
Subject: Re: [RFC PATCH] ALSA: Add debugging guide for audio issues
Date: Tue, 12 Nov 2024 13:26:31 -0700 [thread overview]
Message-ID: <87wmh8p5ag.fsf@trenco.lwn.net> (raw)
In-Reply-To: <109984d7-98f7-4b2a-8fee-1f7b30230a44@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> On 11/7/24 2:25 PM, Jonathan Corbet wrote:
>> If we really want to separate the mechanics of kernel development from
>> the associated process information - not always an easy separation, IMO
>> - we could make a top-level "development" directory, put a lot of the
>> other relevant stuff there, and include the debugging stuff. It seems
>> really weird to put debugging by itself, though; it's only part of the
>> picture.
>
> I could go with that.
>
>>
>> Why is Documentation/process so bad?
>
> Documentation/process/ is meta-documentation about kernel social "standards"
> among other things. It is "soft" documentation, whereas debugging (IMHO) is
> "hard" documentation.
>
> But hey, it's all your baby. Do whatever pleases you. :)
Hopefully not all mine...:)
My suggestion is to put it under process for now just to not block
forward progress on this work. We can surely relocate it if we want to
make a proper development-processes top-level directory in the future.
Thanks,
jon
next prev parent reply other threads:[~2024-11-12 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 20:08 [RFC PATCH] ALSA: Add debugging guide for audio issues anish kumar
2024-11-07 20:45 ` Jonathan Corbet
2024-11-07 21:27 ` Randy Dunlap
2024-11-07 21:40 ` Jonathan Corbet
2024-11-07 21:54 ` Randy Dunlap
2024-11-07 22:25 ` Jonathan Corbet
2024-11-08 4:53 ` Randy Dunlap
2024-11-11 3:37 ` anish kumar
2024-11-12 20:26 ` Jonathan Corbet [this message]
2024-12-06 18:16 ` anish kumar
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=87wmh8p5ag.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rdunlap@infradead.org \
--cc=sebastian.fricke@collabora.com \
--cc=tiwai@suse.com \
--cc=yesanishhere@gmail.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).