netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven-Haegar Koch <haegar@sdinet.de>
To: Jonas Berlin <jberlin@niksula.hut.fi>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: netfilter & ipv6
Date: Thu, 10 Feb 2005 22:36:21 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.62.0502102231060.6223@mercury.sdinet.de> (raw)
In-Reply-To: <420B6A93.3080005@niksula.hut.fi>

On Thu, 10 Feb 2005, Jonas Berlin wrote:

> Jonas Berlin wrote:
>
>> 3. If I succeed porting something, what should I name the patch to be sent 
>> to patch-o-matic-ng? I don't think I could just extend the existing ones as 
>> that would suggest the original authors have something to do with it and 
>> also some of them also are pending or already included in the ekernel. So, 
>> would CLASSIFY_v6 be an acceptable name for the ipv6 version of CLASSIFY?

[...]
> since the name of the name of the module 
> essentially determines the name of the target, the module etc.

why?
the module in patch-o-matic-ng (the top directory name) could be named 
CLASSIFY_v6, containing the target CLASSIFY for ipv6, with the kernel 
module named ip6t_CLASSIFY.
I see nothing which prevents this.

c'ya
sven

-- 

The Internet treats censorship as a routing problem, and routes around it.
(John Gilmore on http://www.cygnus.com/~gnu/)

  parent reply	other threads:[~2005-02-10 21:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  7:50 netfilter & ipv6 Jonas Berlin
2005-02-10 14:07 ` Jonas Berlin
2005-02-10 14:41   ` Samuel Jean
2005-02-10 15:10     ` iptables compile error: NFC_IP_TOS undeclared Alexander Piavka
2005-02-10 15:18       ` Jonas Berlin
2005-02-10 16:00         ` Alexander Piavka
2005-02-10 16:04           ` Jonas Berlin
2005-02-10 17:50             ` Patrick McHardy
2005-02-10 23:16               ` [PATCH] kill NFC_* stuff in iptables [was Re: iptables compile error: NFC_IP_TOS undeclared] Pablo Neira
2005-02-11 19:07                 ` Patrick McHardy
2005-02-11 21:47                   ` Pablo Neira
2005-02-12  1:32                     ` Patrick McHardy
2005-02-12 22:25                       ` Pablo Neira
2005-02-12 23:34                         ` Patrick McHardy
2005-02-10 17:20     ` netfilter & ipv6 Jonas Berlin
2005-02-10 21:36   ` Sven-Haegar Koch [this message]
2005-02-15  1:29     ` Jonas Berlin
     [not found] ` <53965.213.236.112.75.1107867276.squirrel@213.236.112.75>
2005-02-10 23:15   ` ULOG target for ipv6 Jonas Berlin
2005-02-11 22:10     ` netfilter question Pedro Fortuna
2005-02-14 23:25     ` ULOG target for ipv6 Harald Welte
2005-02-15  0:11       ` Jonas Berlin

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=Pine.LNX.4.62.0502102231060.6223@mercury.sdinet.de \
    --to=haegar@sdinet.de \
    --cc=jberlin@niksula.hut.fi \
    --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 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).