Randy Dunlap <rdunlap@xxxxxxxxxxxxx> 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
[Index of Archives]
[Pulseaudio]
[Linux Audio Users]
[ALSA Devel]
[Fedora Desktop]
[Fedora SELinux]
[Big List of Linux Books]
[Yosemite News]
[KDE Users]