From: Patrick McHardy <kaber@trash.net>
To: Phil Oester <kernel@linuxace.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] proto_to_name duplication
Date: Sat, 22 Jul 2006 15:47:40 +0200 [thread overview]
Message-ID: <44C22C7C.2080909@trash.net> (raw)
In-Reply-To: <20060721225612.GA3951@linuxace.com>
Phil Oester wrote:
> Update multiport match to use the iptables version of proto_to_name
> instead of reinventing the wheel.
Also applied, thanks Phil.
> I looked at a similar ipv6 cleanup, but the ipv6header header match
> makes this somewhat trickier.
>
> Incidentally - it's probably time to remove the superfluous mport
> match. Anyone still using it can probably stick with older userspace.
You're probably right, but as long as it doesn't cause any work I
also have no problem with keeping it. Do you know how long ago the
mport patch was removed from pom? Couldn't find anything in the
SVN history.
next prev parent reply other threads:[~2006-07-22 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 22:56 [PATCH] proto_to_name duplication Phil Oester
2006-07-22 13:47 ` Patrick McHardy [this message]
2006-07-22 16:39 ` Phil Oester
2006-07-24 5:38 ` Yasuyuki KOZAKAI
2006-07-24 14:49 ` Phil Oester
2006-07-25 1:21 ` Patrick McHardy
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=44C22C7C.2080909@trash.net \
--to=kaber@trash.net \
--cc=kernel@linuxace.com \
--cc=netfilter-devel@lists.netfilter.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.