From: Eli Carter <eli.carter@inet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] typo in comment
Date: Wed, 22 Aug 2001 13:54:58 -0500 [thread overview]
Message-ID: <3B840002.60D13CEF@inet.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
Alan, (& etc.)
No, it's not terribly important, but in studying the networking code, I
noticed it, so here's a patch against 2.2.19. Please apply. (It's
attached to avoid possible mangling problems.)
Comments, questions, complaints?
Eli
--------------------. Real Users find the one combination of bizarre
Eli Carter \ input values that shuts down the system for days.
eli.carter(a)inet.com `-------------------------------------------------
[-- Attachment #2: spelling.patch --]
[-- Type: text/plain, Size: 667 bytes --]
Index: linux/net/ipv4/route.c
===================================================================
RCS file: /opt/eli_depot/kernelCVS/linux/net/ipv4/route.c,v
retrieving revision 1.1.1.9
diff -u -r1.1.1.9 route.c
--- linux/net/ipv4/route.c 2001/01/20 11:03:27 1.1.1.9
+++ linux/net/ipv4/route.c 2001/08/22 18:47:59
@@ -1346,7 +1346,7 @@
#ifdef CONFIG_IP_ROUTE_VERBOSE
if (IN_DEV_LOG_MARTIANS(in_dev) && net_ratelimit()) {
/*
- * RFC1812 recommenadtion, if source is martian,
+ * RFC1812 recommendation, if source is martian,
* the only hint is MAC header.
*/
printk(KERN_WARNING "martian source %08x for %08x, dev %s\n", saddr, daddr, dev->name);
next reply other threads:[~2001-08-22 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 18:54 Eli Carter [this message]
2001-08-22 19:21 ` [PATCH] typo in comment Evgeny Polyakov
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 13:47 Geert Uytterhoeven
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=3B840002.60D13CEF@inet.com \
--to=eli.carter@inet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.