summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMinghui Liu <minghui.liu.95@gmail.com>2018-02-16 04:03:14 +0300
committerJonathan Corbet <corbet@lwn.net>2018-02-16 17:18:13 +0300
commitbc0ef4a7e4c322ceeee00b1becab966cba7fedb7 (patch)
treed02b0bc15b82a06de3ad7aa75def11ff99a6720b
parent46347502b099d9cff0b635a2eb33c27de9b80b80 (diff)
downloadlinux-bc0ef4a7e4c322ceeee00b1becab966cba7fedb7.tar.xz
Documentation: Delete reference to the kernel-mentors mailing list
Delete reference to the kernel-mentors mailing list because the mailing list no longer exists Signed-off-by: Minghui Liu <minghui.liu.95@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/process/howto.rst7
1 files changed, 0 insertions, 7 deletions
diff --git a/Documentation/process/howto.rst b/Documentation/process/howto.rst
index c6875b1db56f..bcd8d1e2547a 100644
--- a/Documentation/process/howto.rst
+++ b/Documentation/process/howto.rst
@@ -213,13 +213,6 @@ will learn the basics of getting your patch into the Linux kernel tree,
and possibly be pointed in the direction of what to go work on next, if
you do not already have an idea.
-If you already have a chunk of code that you want to put into the kernel
-tree, but need some help getting it in the proper form, the
-kernel-mentors project was created to help you out with this. It is a
-mailing list, and can be found at:
-
- https://selenic.com/mailman/listinfo/kernel-mentors
-
Before making any actual modifications to the Linux kernel code, it is
imperative to understand how the code in question works. For this
purpose, nothing is better than reading through it directly (most tricky