From: Sergey Popovich <popovich_sergei@mail.ua>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ipset: Proposed improvements to the kernel code
Date: Wed, 25 Mar 2015 18:11:26 +0200 [thread overview]
Message-ID: <7893986.4pVhdOQPzb@tuxracer> (raw)
In-Reply-To: <20150325160536.GA4360@salvia>
> On Wed, Mar 25, 2015 at 04:54:54PM +0200, Sergey Popovich wrote:
> Could please send small batch (not more than 10 patches in one go,
> please) to the mailing list so everyone can help in reviewing this?
Not a problem.
My series of patches for nf-next, while Jozsef would like to receive
patches against ipset git tree and rebase may take a while.
Main problem with rebase is that my series implementing RCU, but
this implementation differs from one found in the current ipset git
tree.
This causes excessive number of conflicts, requiring lot of porting
to ipset git tree.
As option I could send only bugfixes to the current nf-next, of course
if Jozsef acknowledges them.
Thanks for the interest.
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter-devel"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
SP5474-RIPE
Sergey Popovich
next prev parent reply other threads:[~2015-03-25 16:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 13:29 ipset: Proposed improvements to the kernel code Sergey Popovich
2015-03-16 19:30 ` Jozsef Kadlecsik
2015-03-17 4:46 ` Sergey Popovich
2015-03-17 12:31 ` Jozsef Kadlecsik
2015-03-17 13:23 ` Sergey Popovich
2015-03-17 14:45 ` Jozsef Kadlecsik
2015-03-17 18:59 ` Sergey Popovich
2015-03-18 19:59 ` Jozsef Kadlecsik
2015-03-25 14:54 ` Sergey Popovich
2015-03-25 16:05 ` Pablo Neira Ayuso
2015-03-25 16:11 ` Sergey Popovich [this message]
2015-03-26 11:26 ` Pablo Neira Ayuso
2015-03-26 22:10 ` Jozsef Kadlecsik
2015-03-27 7:41 ` Sergey Popovich
2015-03-28 20:44 ` 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=7893986.4pVhdOQPzb@tuxracer \
--to=popovich_sergei@mail.ua \
--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).