From: Qinghuang Feng <qhfeng.kernel@gmail.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] NET: fix wrong English expression in comments
Date: Mon, 12 Jan 2009 02:36:59 +0800 [thread overview]
Message-ID: <496a3c51.09876e0a.03fe.7e80@mx.google.com> (raw)
Signed-off-by: Qinghuang Feng <qhfeng.kernel@gmail.com>
---
diff --git a/include/net/inet_timewait_sock.h b/include/net/inet_timewait_sock.h
index 4b8ece2..2540d3a 100644
--- a/include/net/inet_timewait_sock.h
+++ b/include/net/inet_timewait_sock.h
@@ -103,7 +103,7 @@ struct inet_bind_bucket;
struct inet_timewait_sock {
/*
* Now struct sock also uses sock_common, so please just
- * don't add nothing before this first member (__tw_common) --acme
+ * don't add anything before this first member (__tw_common) --acme
*/
struct sock_common __tw_common;
#define tw_family __tw_common.skc_family
diff --git a/include/net/sock.h b/include/net/sock.h
index 5a3a151..a587e9d 100644
--- a/include/net/sock.h
+++ b/include/net/sock.h
@@ -204,7 +204,7 @@ struct sock_common {
struct sock {
/*
* Now struct inet_timewait_sock also uses sock_common, so please just
- * don't add nothing before this first member (__sk_common) --acme
+ * don't add anything before this first member (__sk_common) --acme
*/
struct sock_common __sk_common;
#define sk_family __sk_common.skc_family
next reply other threads:[~2009-01-11 18:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 18:36 Qinghuang Feng [this message]
2009-01-12 1:05 ` [PATCH] NET: fix wrong English expression in comments Li Zefan
2009-01-12 1:39 ` Ben Hutchings
2009-01-13 5:53 ` David Miller
2009-01-13 6:16 ` Daolong Wang
2009-01-13 8:41 ` David Newall
2009-01-13 9:04 ` Alan Cox
2009-01-13 12:09 ` David Newall
2009-01-13 23:22 ` Valdis.Kletnieks
2009-01-13 23:30 ` Randy Dunlap
[not found] ` <6b1ba94c0901122336r511fa316o5f520a8d2d9d6e0@mail.gmail.com>
2009-01-13 7:44 ` David Miller
2009-01-13 7:56 ` Li Zefan
2009-01-13 7:57 ` Eric Dumazet
2009-01-13 8:52 ` Oliver Hartkopp
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=496a3c51.09876e0a.03fe.7e80@mx.google.com \
--to=qhfeng.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).