From: Li Zefan <lizf@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Li Xiaodong <lixd@cn.fujitsu.com>,
linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>,
linux-net@vger.kernel.org
Subject: [PATCH] Documentation/sysctl/net.txt: fix a typo
Date: Tue, 07 Apr 2009 13:28:45 +0800 [thread overview]
Message-ID: <49DAE48D.3070408@cn.fujitsu.com> (raw)
In-Reply-To: <49D40D67.9020909@cn.fujitsu.com>
Li Zefan wrote:
>> -There are only two files in this subdirectory. They control the delays for
>> -deleting and destroying socket descriptors.
>> +There is only one file in this directory.
>> +unix_dgram_qlen limits the max number of datagrams queued in Unix domain
>> +socket's buffer. It will not take effect unless PF_UNIX flag is spicified.
>>
>
> s/spicified/specified
>
sigh..This slipped into mainline..let's fix it.
================
s/spicified/specified
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
---
Documentation/sysctl/net.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/sysctl/net.txt b/Documentation/sysctl/net.txt
index a34d55b..df38ef0 100644
--- a/Documentation/sysctl/net.txt
+++ b/Documentation/sysctl/net.txt
@@ -95,7 +95,7 @@ of struct cmsghdr structures with appended data.
There is only one file in this directory.
unix_dgram_qlen limits the max number of datagrams queued in Unix domain
-socket's buffer. It will not take effect unless PF_UNIX flag is spicified.
+socket's buffer. It will not take effect unless PF_UNIX flag is specified.
3. /proc/sys/net/ipv4 - IPV4 settings
--
1.5.4.rc3
prev parent reply other threads:[~2009-04-07 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 9:55 [PATCH] Update Documentation: unix_dgram_qlen@proc.txt Li Xiaodong
2009-04-02 0:57 ` Li Zefan
2009-04-07 5:28 ` Li Zefan [this message]
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=49DAE48D.3070408@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=lixd@cn.fujitsu.com \
/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