From: Massimiliano Hofer <max@nucleus.it>
To: netfilter-devel@lists.netfilter.org
Cc: Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH] priv_data (formerly entry_data)
Date: Wed, 21 Jun 2006 10:31:50 +0200 [thread overview]
Message-ID: <200606211031.51291.max@nucleus.it> (raw)
In-Reply-To: <44989B26.8070704@trash.net>
On Wednesday 21 June 2006 3:04 am, Patrick McHardy wrote:
> >>I think this should be done somewhere in x_tables. I think I would
> >>rename xt_check_match to xt_init_match, put the allocation there
> >>and finally rename ->checkentry to ->init .. the name doesn't really
> >>fit anymore since people started doing real initialization in there,
> >>and changing prototypes is a good opportunity for fixing that.
> >
> > I was wandering why it was duplicated between IPv4 and IPv6.
>
> Do you mean the check_match functions and the ->checkentry calls?
> The only reason is because they use a different type for the "ip"
> argument.
No, I noticed several functions in ip_tables.c and ip6_tables.c that
differentiate only by having struct ipt_entry_match * instead of struct
ip6t_entry_match *, while they're both defines to xt_entry_match (the same
goes for xt_entry_target).
I've not checked it throu yet, but I think that most of them could be moved to
x_tables.c.
> > Are these changes planned for 2.6.18?
>
> I was hoping you could do it while you're changing this stuff ..
> I'd like to avoid touching all >30 files twice for a related
> change.
OK, I didn't know if someone else was already at work.
I can't do it today, though. I hope I'll start working on it tomorrow.
--
Saluti,
Massimiliano Hofer
Nucleus
next prev parent reply other threads:[~2006-06-21 8:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 22:29 [PATCH] entry_data Massimiliano Hofer
2006-06-11 23:19 ` Massimiliano Hofer
2006-06-12 9:50 ` Pablo Neira Ayuso
2006-06-12 12:45 ` Massimiliano Hofer
2006-06-13 15:19 ` Pablo Neira Ayuso
2006-06-13 20:56 ` Massimiliano Hofer
2006-06-19 0:15 ` Pablo Neira Ayuso
2006-06-19 7:02 ` Massimiliano Hofer
2006-06-19 23:37 ` Pablo Neira Ayuso
2006-06-20 1:39 ` Patrick McHardy
2006-06-14 9:03 ` Sven Anders
2006-06-17 22:55 ` Massimiliano Hofer
2006-06-19 17:45 ` Patrick McHardy
2006-06-19 23:05 ` Massimiliano Hofer
2006-06-20 1:29 ` Patrick McHardy
2006-06-19 17:34 ` Patrick McHardy
2006-06-19 22:35 ` Massimiliano Hofer
2006-06-19 23:13 ` Patrick McHardy
2006-06-20 11:25 ` Massimiliano Hofer
2006-06-20 13:17 ` Patrick McHardy
2006-06-21 0:03 ` [PATCH] priv_data (formerly entry_data) Massimiliano Hofer
2006-06-21 0:30 ` Patrick McHardy
2006-06-21 0:45 ` Massimiliano Hofer
2006-06-21 1:04 ` Patrick McHardy
2006-06-21 8:31 ` Massimiliano Hofer [this message]
2006-06-21 23:50 ` Massimiliano Hofer
2006-06-22 15:18 ` Patrick McHardy
2006-06-21 0:33 ` Massimiliano Hofer
2006-06-21 0:42 ` Massimiliano Hofer
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=200606211031.51291.max@nucleus.it \
--to=max@nucleus.it \
--cc=kaber@trash.net \
--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.