From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nf-next: cleanups, err reporting (rd.2)
Date: Thu, 25 Mar 2010 13:48:36 +0100 [thread overview]
Message-ID: <4BAB5BA4.3090007@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1003231734040.19672@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> On Monday 2010-03-22 20:17, Jan Engelhardt wrote:
>> Jan Engelhardt (9):
>> netfilter: xtables: make use of caller family rather than target family
>> netfilter: xt extensions: use pr_<level> (2)
>> netfilter: xtables: make use of xt_request_find_target
>> netfilter: xtables: consolidate code into xt_request_find_match
>> netfilter: xt_recent: allow changing ip_list_[ug]id at runtime
>
> I have incorporated your comments; as I'm still on with the error reporting
> pieces, here is the batch of five instead:
> Please merge.
>
>
> The following changes since commit 2c46cd8163b25bf6f38e612e9f1d162f0357c8f1:
> Zhitong Wang (1):
> netfilter: remove unused headers in net/ipv4/netfilter/nf_nat_h323.c
>
> are available in the git repository at:
>
> git://dev.medozas.de/linux master
>
> Jan Engelhardt (5):
> netfilter: xtables: make use of caller family rather than target family
> netfilter: xt extensions: use pr_<level> (2)
> netfilter: xtables: make use of xt_request_find_target
> netfilter: xtables: consolidate code into xt_request_find_match
> netfilter: xt_recent: allow changing ip_list_[ug]id at runtime
Please repost these patches, I have a few more comments but I'd like
to make sure they're still relevant for the latest patchset.
prev parent reply other threads:[~2010-03-25 12:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 19:17 nf-next: cleanups, err reporting (rd.2) Jan Engelhardt
2010-03-22 19:17 ` [PATCH 1/9] netfilter: xtables: make use of caller family rather than target family Jan Engelhardt
2010-03-22 19:17 ` [PATCH 2/9] netfilter: xt extensions: use pr_<level> (2) Jan Engelhardt
2010-03-22 19:17 ` [PATCH 3/9] netfilter: xtables: make use of xt_request_find_target Jan Engelhardt
2010-03-23 14:24 ` Patrick McHardy
2010-03-23 14:27 ` Jan Engelhardt
2010-03-22 19:18 ` [PATCH 4/9] netfilter: xtables: consolidate code into xt_request_find_match Jan Engelhardt
2010-03-23 14:27 ` Patrick McHardy
2010-03-22 19:18 ` [PATCH 5/9] netfilter: xt_recent: allow changing ip_list_[ug]id at runtime Jan Engelhardt
2010-03-23 14:18 ` Patrick McHardy
2010-03-23 14:23 ` Jan Engelhardt
2010-03-23 14:55 ` Patrick McHardy
2010-03-23 15:06 ` Jan Engelhardt
2010-03-23 15:10 ` Patrick McHardy
2010-03-22 19:18 ` [PATCH 6/9] netfilter: xtables: slightly better error reporting (1/2) Jan Engelhardt
2010-03-22 19:18 ` [PATCH 7/9] netfilter: xtables: slightly better error reporting (2/2) Jan Engelhardt
2010-03-23 14:44 ` Patrick McHardy
2010-03-23 15:00 ` Jan Engelhardt
2010-03-23 15:02 ` Patrick McHardy
2010-03-22 19:18 ` [PATCH 8/9] netfilter: xtables: use only error codes for checkentry Jan Engelhardt
2010-03-22 19:18 ` [PATCH 9/9] netfilter: xtables: shorten up return clause Jan Engelhardt
2010-03-23 16:35 ` nf-next: cleanups, err reporting (rd.2) Jan Engelhardt
2010-03-25 12:48 ` Patrick McHardy [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=4BAB5BA4.3090007@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--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).