From: Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Core Team <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] ipset: add "inner" flag support
Date: Fri, 05 Jul 2013 21:33:32 +0100 [thread overview]
Message-ID: <51D72D9B.9040003@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1307052001200.20246@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> I have just noticed one single issue with your patches: the revision
> bumping for the set types are missing.
>
Interesting. I wasn't aware you've introduced this feature and by
looking at the logs, this has been present since 6.14 - shame on me for
not noticing it.
> So please extend the second patch with the type revisions incremented
> (have a look at the hash:net type how the revision comments are kept)
> and add a userspace patch with the revisions bumped in userspace too (it's
> fine to copy the most recent ones and increase the revisions, adjust the
> descriptions).
In other words, something like:
kernel/net/netfilter/ip_set_*.c
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-#define IPSET_TYPE_REV_MAX 3 /* Counters support added */
+/* 3 Counters support added */
+#define IPSET_TYPE_REV_MAX 4 /* Inner flag support added */
lib/ipset_*.c
~~~~~~~~~~~~~
copy the entire ipset_hash_netX struct, bump the ".revision" and adjust
the ".description" fields?
Would that suffice?
Also, would you like me to modify my 3rd patch (which is where I've made
the changes to all sets - in patch two I reimplemented the "internal"
functions) and issue a separate one for all lib/ipset_*.c changes or
would you like me to reissue the whole set of patches (1-6)?
> That's all and then the patchset is ready for inclusion.
>
Thanks.
next prev parent reply other threads:[~2013-07-05 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 21:32 [PATCH v3 0/5] ipset: add "inner" flag support Dash Four
2013-07-05 18:06 ` Jozsef Kadlecsik
2013-07-05 20:33 ` Dash Four [this message]
2013-07-05 20:48 ` Jozsef Kadlecsik
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=51D72D9B.9040003@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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).