From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: Patrick McHardy <kaber@trash.net>
Cc: timg@tpi.com, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] xt_recent: Fix false hit_count match
Date: Mon, 22 Mar 2010 20:14:31 +0100 [thread overview]
Message-ID: <4BA7C197.3030609@intra2net.com> (raw)
In-Reply-To: <4BA7A967.9060308@trash.net>
On 03/22/2010 06:31 PM, Patrick McHardy wrote:
>> Clearly your new version is more readable about the intent.
>
> Thomas, before I send this upstream with a Tested-by tag in your name,
> could you please confirm that this is the change you've actually tested?
Yes and I just did another test run with your final patch, works fine.
Cheers,
Thomas
prev parent reply other threads:[~2010-03-22 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 17:49 [PATCH] xt_recent: Fix false hit_count match Tim Gardner
2010-02-23 13:59 ` Patrick McHardy
2010-03-19 15:04 ` Thomas Jarosch
2010-03-19 15:41 ` Patrick McHardy
2010-03-19 16:14 ` Tim Gardner
2010-03-19 16:19 ` Thomas Jarosch
2010-03-19 16:32 ` Patrick McHardy
2010-03-19 16:38 ` Tim Gardner
2010-03-22 17:31 ` Patrick McHardy
2010-03-22 19:14 ` Thomas Jarosch [this message]
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=4BA7C197.3030609@intra2net.com \
--to=thomas.jarosch@intra2net.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=timg@tpi.com \
/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).