linux-kernel - Re: [RFC PATCH] ALSA: Add debugging guide for audio issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87v7wyznow.fsf@trenco.lwn.net>
Date: Thu, 07 Nov 2024 15:25:19 -0700
From: Jonathan Corbet <corbet@....net>
To: Randy Dunlap <rdunlap@...radead.org>, anish kumar
 <yesanishhere@...il.com>, lgirdwood@...il.com, broonie@...nel.org,
 perex@...ex.cz, tiwai@...e.com, Sebastian Fricke
 <sebastian.fricke@...labora.com>
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-sound@...r.kernel.org
Subject: Re: [RFC PATCH] ALSA: Add debugging guide for audio issues

Randy Dunlap <rdunlap@...radead.org> writes:

> I see a few possibilities, none perfect:
>
> a. in Documentation/driver-api/debug/  [not quite driver-api though]

No, it's not API stuff, and not limited to drivers.

> b. in Documentation/core-api/ along with debugging-via-ohci1394.rst
> [maybe in a new /debug/ subdir]

Again, not really API stuff.

> c. in (new) Documentation/debug/ and invite the kernel debugging
> community to add some of their docs here as well.

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.

Why is Documentation/process so bad?

Thanks,

jon