public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Frazer <mark@somanetworks.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/kernel-docs.txt
Date: Mon, 28 May 2001 12:41:57 -0400	[thread overview]
Message-ID: <20010528124157.C30332@somanetworks.com> (raw)
In-Reply-To: <20010528122601.A945@somanetworks.com>
In-Reply-To: <20010528122601.A945@somanetworks.com>; from mark@somanetworks.com on Mon, May 28, 2001 at 12:26:01PM -0400

Oops, that was wrong.  The proper patch is:

--- Documentation/kernel-docs.txt.old   Mon May 28 12:06:43 2001
+++ Documentation/kernel-docs.txt       Mon May 28 12:37:26 2001
@@ -333,7 +333,8 @@
        
      * Title: "The Kernel Hacking HOWTO"
        Author: Various Talented People, and Rusty.
-       URL: http://www.samba.org/~netfilter/kernel-hacking-HOWTO.html
+       URL: http://netfilter.gnumonks.org/unreliable-guides/kernel-hacking/
+               lk-hacking-guide.html
        Keywords: HOWTO, kernel contexts, deadlock, locking, modules,
        symbols, return conventions.
        Description: From the Introduction: "Please understand that I
@@ -393,9 +394,8 @@
        
      * Title: "Linux Kernel Locking HOWTO"
        Author: Various Talented People, and Rusty.
-       URL:
-       http://netfilter.kernelnotes.org/unreliable-guides/kernel-locking-
-       HOWTO.html
+       URL: http://netfilter.gnumonks.org/unreliable-guides/kernel-locking/
+               lklockingguide.html
        Keywords: locks, locking, spinlock, semaphore, atomic, race
        condition, bottom halves, tasklets, softirqs.
        Description: The title says it all: document describing the


           reply	other threads:[~2001-05-28 16:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20010528122601.A945@somanetworks.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010528124157.C30332@somanetworks.com \
    --to=mark@somanetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox