From: Rick Jones <rick.jones2@hp.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] Update function names in /proc/net/tcp documentation
Date: Fri, 12 Oct 2007 16:13:32 -0700 [thread overview]
Message-ID: <470FFF9C.7040402@hp.com> (raw)
In-Reply-To: <20071012225426.2f866ae6@hyperion.delvare>
Jean Delvare wrote:
> Update function name references to match the current code.
>
> Signed-off-by: Jean Delvare <khali@linux-fr.org>
> ---
> Documentation/networking/proc_net_tcp.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-2.6.23.orig/Documentation/networking/proc_net_tcp.txt 2007-02-04 19:44:54.000000000 +0100
> +++ linux-2.6.23/Documentation/networking/proc_net_tcp.txt 2007-10-12 22:50:15.000000000 +0200
> @@ -1,8 +1,8 @@
> This document describes the interfaces /proc/net/tcp and /proc/net/tcp6.
>
> These /proc interfaces provide information about currently active TCP
> -connections, and are implemented by tcp_get_info() in net/ipv4/tcp_ipv4.c and
> -tcp6_get_info() in net/ipv6/tcp_ipv6.c, respectively.
> +connections, and are implemented by tcp4_seq_show() in net/ipv4/tcp_ipv4.c
> +and tcp6_seq_show() in net/ipv6/tcp_ipv6.c, respectively.
>
> It will first list all listening TCP sockets, and next list all established
> TCP connections. A typical entry of /proc/net/tcp would look like this (split
/proc/net/[tcp|tcp6] are deprecated now right? Perhaps there should be
something to that effect added to the txt.
rick jones
next prev parent reply other threads:[~2007-10-12 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 20:54 [PATCH] Update function names in /proc/net/tcp documentation Jean Delvare
2007-10-12 23:13 ` Rick Jones [this message]
2007-10-13 12:43 ` Jean Delvare
2007-10-13 12:49 ` Herbert Xu
2007-10-14 9:59 ` Jean Delvare
2007-10-14 10:09 ` Herbert Xu
2007-10-16 8:46 ` Jean Delvare
2007-10-16 10:34 ` Herbert Xu
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=470FFF9C.7040402@hp.com \
--to=rick.jones2@hp.com \
--cc=khali@linux-fr.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 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.