netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Popovich <popovich_sergei@mail.ua>
To: netfilter-devel@vger.kernel.org
Cc: kadlec@blackhole.kfki.hu
Subject: Re: ipset: Proposed improvements to the kernel code
Date: Wed, 25 Mar 2015 16:54:54 +0200	[thread overview]
Message-ID: <14722035.jXe0WcxyPC@tuxracer> (raw)
In-Reply-To: <4532245.8hNB4lJHyg@tuxracer>

> > > I did not say that you should do anything, I just give an option (like
> > > branch) to let you quickly see changes I made if you wish. Maybe you
> > > find them totally useless:)
> > 
> > I see - a branch costs nothing, so that's no problem. Then create a
> > numbered list of the patches, put them in a tar file and let me know from
> > where I can download it.
> 
> Thanks Jozsef, I have prepare patches for you and put link to the series.
> 
> http://ftp.payport.com.ua/users/sergey/public/netfilter-devel-2015031701.tar
> 
> These patches will be against nf-next for simplicity and I'm already rebase
> them, so for first review just fresh nf-next will be needed.
> 

Fixes to the first series. One of the most important is the fixes to set and 
their data netlink dumping consistency. Just to complete series.

Netlink dumping consistency was inspired by the recent ipset git tree fixes
to this problem. However I think there are other problems with consistent
data dumping exists which my series tries to addess.

As the first series this is for nf-next git tree, not ipset git tree.

http://ftp.payport.com.ua/users/sergey/public/netfilter-devel-2015032501.tar

> Then new changes from the ipset-next could be backported into ipset git tree
> (say it would be named as ipset-stable to the analogy with linux-stable
> etc.).
> > Best regards,
> > Jozsef
> > -
> > E-mail  : kadlec@blackhole.kfki.hu, kadlecsik.jozsef@wigner.mta.hu
> > PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
> > Address : Wigner Research Centre for Physics, Hungarian Academy of
> > Sciences
> > 
> >           H-1525 Budapest 114, POB. 49, Hungary

-- 
SP5474-RIPE
Sergey Popovich


  parent reply	other threads:[~2015-03-25 15:31 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 [this message]
2015-03-25 16:05               ` Pablo Neira Ayuso
2015-03-25 16:11                 ` Sergey Popovich
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=14722035.jXe0WcxyPC@tuxracer \
    --to=popovich_sergei@mail.ua \
    --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;
as well as URLs for NNTP newsgroup(s).