From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Patrick McHardy <kaber@trash.net>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH iptables] extensions: libxt_rateest: fix bps options for iptables-save
Date: Thu, 15 Jul 2010 19:14:36 +0300 [thread overview]
Message-ID: <1279210476.1575.1.camel@powerslave> (raw)
In-Reply-To: <4C3F32FD.6050706@trash.net>
On Thu, 2010-07-15 at 18:10 +0200, ext Patrick McHardy wrote:
> Am 15.07.2010 18:04, schrieb Luciano Coelho:
> > The output generated by the libxt_rateest extension for bps matches
> > was wrong and could not be restored properly. This patch fixes this
> > problem by using the correct options in the right order when saving
> > the table.
>
> Applied, thanks.
A quick question: do you apply this to iptables-next? Or iptables-next
will only be aligned with master when you merge them (when the stuff
included in iptables-next gets released in the kernel)?
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-07-15 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 16:04 [PATCH iptables] extensions: libxt_rateest: fix bps options for iptables-save Luciano Coelho
2010-07-15 16:10 ` Patrick McHardy
2010-07-15 16:14 ` Luciano Coelho [this message]
2010-07-15 16:17 ` 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=1279210476.1575.1.camel@powerslave \
--to=luciano.coelho@nokia.com \
--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.