All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart De Schuymer <bdschuym@pandora.be>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Patrick McHardy <kaber@trash.net>,
	Netfilter Developer Mailing List
	<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH 1/4] [NETFILTER]: ebtables: expand/remove unneeded macros
Date: Sun, 20 Jan 2008 19:07:21 +0100	[thread overview]
Message-ID: <1200852441.2894.30.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0801201815160.14598@fbirervta.pbzchgretzou.qr>

Op zo, 20-01-2008 te 18:34 +0100, schreef Jan Engelhardt:
> "Ugh." I do not think ebtables(8) should depend on such macros.
> iptables(8) does not do that either.
> What good would those macros be for? It is not like the module names
> would be changing anyway (one purpose of macros - to reduce the number
> of places where you have to change things iff things change).

We are talking about EBT_ENTRY_ITERATE and the like, right?
I didn't see your patch, but even the kernel code uses the ITERATE
macros more than once.

> >> For the
> >> other patches I have no objection except that the MODULE_DESCRIPTION
> >> isn't consistent with using upper case after 'Ebtables: ', but I guess
> >> that's nitpicking :) Anyway, thanks Jan.
> 
> It is consistent...
> 
> 18:17 ichi:~/Coding/linux_nosov > git log -p
> 4ad299b1644579e5c9aae025bf81f6aff1cbdc77^..4ad299b1644579e5c9aae025bf81f6aff1cbdc77
> | grep MODULE_DESC | grep ^+
> 
> +MODULE_DESCRIPTION("Ebtables: DSAP/SSAP field and SNAP type matching");
> +MODULE_DESCRIPTION("Ebtables: Combined MAC/IP address list matching");
> +MODULE_DESCRIPTION("Ebtables: ARP protocol packet match");
> +MODULE_DESCRIPTION("Ebtables: ARP reply target");
> +MODULE_DESCRIPTION("Ebtables: Destination MAC address translation");
> +MODULE_DESCRIPTION("Ebtables: IPv4 protocol packet match");
> +MODULE_DESCRIPTION("Ebtables: rate-limit match");
> +MODULE_DESCRIPTION("Ebtables: Packet logging to syslog");
> +MODULE_DESCRIPTION("Ebtables: packet mark modification");

packet vs Packet, rate vs Packet, ... But this is not worth the
bandwidth at all, I should just shut up :)

> > But since ebtables, arptables and iptables
> > are pretty similar, perhaps it would be possible to merge ebtables
> > and arptables support with iptables.
> 
> Before you attempt that, try merging ip- with ip6tables first.

And arptables before ebtables :)
For ebtables it's probably best to drop binary compatibility with older
ebtables userspace binaries, it's gonna be a mess if you don't.

cheers,
Bart



  reply	other threads:[~2008-01-20 18:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 20:10 [PATCH 1/4] [NETFILTER]: ebtables: expand/remove unneeded macros Jan Engelhardt
2008-01-17 20:10 ` [PATCH 2/4] [NETFILTER]: ebtables: remove casts, use consts Jan Engelhardt
2008-01-20 14:52   ` Patrick McHardy
2008-01-17 20:11 ` [PATCH 3/4] [NETFILTER]: ebtables: mark matches, targets and watchers __read_mostly Jan Engelhardt
2008-01-20 14:52   ` Patrick McHardy
2008-01-20 18:07     ` Jan Engelhardt
2008-01-20 18:21       ` Patrick McHardy
2008-01-22 17:02   ` Patrick McHardy
2008-01-17 20:11 ` [PATCH 4/4] [NETFILTER]: ebtables: Update modules' descriptions Jan Engelhardt
2008-01-20 14:54   ` Patrick McHardy
2008-01-20 13:02 ` [PATCH 1/4] [NETFILTER]: ebtables: expand/remove unneeded macros Patrick McHardy
2008-01-20 13:09   ` Jan Engelhardt
2008-01-20 13:17     ` Patrick McHardy
2008-01-20 14:26       ` Bart De Schuymer
2008-01-20 14:45         ` Patrick McHardy
2008-01-20 17:34           ` Jan Engelhardt
2008-01-20 18:07             ` Bart De Schuymer [this message]
2008-01-20 18:30               ` Jan Engelhardt
2008-01-20 18:57                 ` Bart De Schuymer
2008-01-20 19:03                   ` Jan Engelhardt
2008-01-24  8:05                 ` 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=1200852441.2894.30.camel@localhost.localdomain \
    --to=bdschuym@pandora.be \
    --cc=jengelh@computergmbh.de \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@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 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.