From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] Reserve nfnetlink subsys ids.
Date: Thu, 11 Jun 2009 16:08:52 +0200 [thread overview]
Message-ID: <4A310FF4.2070207@trash.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0906111334090.28605@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> Hi Patrick,
>
> A tiny patch to add nfnetlink subsys ids for nftables and ipset. :-)
Its usually frowned upon to reserve IDs that are not used yet.
We can certainly coordinate so nftables and ipset won't clash
unless we add a different subsystem (we actually did, OSF is
new in nf-next-2.6.git). But is there a reason for adding the
IPSET id at this time instead of waiting until we merge it?
next prev parent reply other threads:[~2009-06-11 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 11:36 [PATCH] Reserve nfnetlink subsys ids Jozsef Kadlecsik
2009-06-11 14:08 ` Patrick McHardy [this message]
2009-06-11 14:26 ` Pablo Neira Ayuso
2009-06-11 14:43 ` Pablo Neira Ayuso
2009-06-11 14:49 ` Patrick McHardy
2009-06-11 21:51 ` Jozsef Kadlecsik
2009-06-12 12:08 ` Patrick McHardy
2009-06-12 13:02 ` Jozsef Kadlecsik
2009-06-12 13:07 ` Patrick McHardy
2009-06-12 13:18 ` Jan Engelhardt
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=4A310FF4.2070207@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox