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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Thu, 15 Feb 2018 16:05:37 -0800
From:   Minghui Liu <minghui.liu.95@...il.com>
To:     corbet@....net
Cc:     sj38.park@...il.com, mchehab@...nel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, trivial@...nel.org
Subject: [PATCH] Documentation: Delete reference to the kernel-mentors mailing
 list because the mailing list no longer exists

From 2e4a473973a3b2dd841dc73523766c45f990acb5 Mon Sep 17 00:00:00 2001
From: Minghui Liu <minghui.liu.95@...il.com>
Date: Thu, 15 Feb 2018 18:33:14 -0500
Subject: [PATCH] Documentation: Delete reference to the kernel-mentors mailing
 list because the mailing list no longer exists

Signed-off-by: Minghui Liu <minghui.liu.95@...il.com>
---
 Documentation/process/howto.rst | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/Documentation/process/howto.rst b/Documentation/process/howto.rst
index c6875b1..bcd8d1e 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
-- 
1.8.3.1


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ