From: David Miller <davem@davemloft.net>
To: xemul@openvz.org
Cc: netdev@vger.kernel.org, devel@openvz.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH 6/6 net-2.6.25][RAW] Consolidate proc interface (v2)
Date: Mon, 19 Nov 2007 22:38:43 -0800 (PST) [thread overview]
Message-ID: <20071119.223843.100278186.davem@davemloft.net> (raw)
In-Reply-To: <473DB1E8.60902@openvz.org>
From: Pavel Emelyanov <xemul@openvz.org>
Date: Fri, 16 Nov 2007 18:06:16 +0300
> Both ipv6/raw.c and ipv4/raw.c use the seq files to walk
> through the raw sockets hash and show them.
>
> The "walking" code is rather huge, but is identical in both
> cases. The difference is the hash table to walk over and
> the protocol family to check (this was not in the first
> virsion of the patch, which was noticed by YOSHIFUJI)
>
> Make the ->open store the needed hash table and the family
> on the allocated raw_iter_state and make the start/next/stop
> callbacks work with it.
>
> This removes most of the code.
>
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Also applied, thanks a lot.
prev parent reply other threads:[~2007-11-20 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 15:06 [PATCH 6/6 net-2.6.25][RAW] Consolidate proc interface (v2) Pavel Emelyanov
2007-11-20 6:38 ` David Miller [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=20071119.223843.100278186.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.org \
--cc=yoshfuji@linux-ipv6.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).