|author||Henrik Austad <email@example.com>||2018-09-04 00:15:23 +0200|
|committer||Jonathan Corbet <firstname.lastname@example.org>||2018-09-09 15:08:58 -0600|
Drop all 00-INDEX files from Documentation/
This is a respin with a wider audience (all that get_maintainer returned) and I know this spams a *lot* of people. Not sure what would be the correct way, so my apologies for ruining your inbox. The 00-INDEX files are supposed to give a summary of all files present in a directory, but these files are horribly out of date and their usefulness is brought into question. Often a simple "ls" would reveal the same information as the filenames are generally quite descriptive as a short introduction to what the file covers (it should not surprise anyone what Documentation/sched/sched-design-CFS.txt covers) A few years back it was mentioned that these files were no longer really needed, and they have since then grown further out of date, so perhaps it is time to just throw them out. A short status yields the following _outdated_ 00-INDEX files, first counter is files listed in 00-INDEX but missing in the directory, last is files present but not listed in 00-INDEX. List of outdated 00-INDEX: Documentation: (4/10) Documentation/sysctl: (0/1) Documentation/timers: (1/0) Documentation/blockdev: (3/1) Documentation/w1/slaves: (0/1) Documentation/locking: (0/1) Documentation/devicetree: (0/5) Documentation/power: (1/1) Documentation/powerpc: (0/5) Documentation/arm: (1/0) Documentation/x86: (0/9) Documentation/x86/x86_64: (1/1) Documentation/scsi: (4/4) Documentation/filesystems: (2/9) Documentation/filesystems/nfs: (0/2) Documentation/cgroup-v1: (0/2) Documentation/kbuild: (0/4) Documentation/spi: (1/0) Documentation/virtual/kvm: (1/0) Documentation/scheduler: (0/2) Documentation/fb: (0/1) Documentation/block: (0/1) Documentation/networking: (6/37) Documentation/vm: (1/3) Then there are 364 subdirectories in Documentation/ with several files that are missing 00-INDEX alltogether (and another 120 with a single file and no 00-INDEX). I don't really have an opinion to whether or not we /should/ have 00-INDEX, but the above 00-INDEX should either be removed or be kept up to date. If we should keep the files, I can try to keep them updated, but I rather not if we just want to delete them anyway. As a starting point, remove all index-files and references to 00-INDEX and see where the discussion is going. Signed-off-by: Henrik Austad <email@example.com> Acked-by: "Paul E. McKenney" <firstname.lastname@example.org> Just-do-it-by: Steven Rostedt <email@example.com> Reviewed-by: Jens Axboe <firstname.lastname@example.org> Acked-by: Paul Moore <email@example.com> Acked-by: Greg Kroah-Hartman <firstname.lastname@example.org> Acked-by: Mark Brown <email@example.com> Acked-by: Mike Rapoport <firstname.lastname@example.org> Cc: [Almost everybody else] Signed-off-by: Jonathan Corbet <email@example.com>
Diffstat (limited to 'Documentation/locking')
1 files changed, 0 insertions, 16 deletions
diff --git a/Documentation/locking/00-INDEX b/Documentation/locking/00-INDEX
deleted file mode 100644
@@ -1,16 +0,0 @@
- - this file.
- - documentation on the runtime locking correctness validator.
- - info on collecting statistics on locks (and contention).
- - info on the generic mutex subsystem.
- - description of the RealTime mutex implementation design.
- - desc. of RT-mutex subsystem with PI (Priority Inheritance) support.
- - info on using spinlocks to provide exclusive access in kernel.
- - Intro to Mutex wait/would deadlock handling.s