From: "Denis V. Lunev" <den@openvz.org>
To: David Miller <davem@davemloft.net>
Cc: Netdev List <netdev@vger.kernel.org>
Subject: [TCP 0/6 net-2.6.26]: tcp_proc_register simplification.
Date: Tue, 08 Apr 2008 17:28:38 +0400 [thread overview]
Message-ID: <1207661318.7171.22.camel@iris.sw.ru> (raw)
I have found that tcp_proc_register looks in the same way as
udp_proc_register. So, I have ported improvements made in the commits
6f191efe48af62dd5f8917dd21d187f896cd6c81..4ad96d39a2d74c1b2e400b602da2594f5098fc26
to TCP.
Signed-off-by: Denis V. Lunev <den@openvz.org>
next reply other threads:[~2008-04-08 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 13:28 Denis V. Lunev [this message]
2008-04-08 13:29 ` [PATCH] [TCP]: Replace struct net on tcp_iter_state with seq_net_private Denis V. Lunev
2008-04-08 13:29 ` [PATCH] [TCP]: No need to check afinfo != NULL in tcp_proc_(un)register Denis V. Lunev
2008-04-08 13:29 ` [PATCH] [TCP]: Move seq_ops from tcp_iter_state to tcp_seq_afinfo Denis V. Lunev
2008-04-08 13:29 ` [PATCH] [TCP]: Cleanup /proc/tcp[6] creation/removal Denis V. Lunev
2008-04-08 13:29 ` [PATCH] [TCP]: Place file operations directly into tcp_seq_afinfo Denis V. Lunev
2008-04-08 13:29 ` [PATCH] [TCP]: Remove owner from tcp_seq_afinfo Denis V. Lunev
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=1207661318.7171.22.camel@iris.sw.ru \
--to=den@openvz.org \
--cc=davem@davemloft.net \
--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).