From: Bart De Schuymer <bdschuym@pandora.be>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: kaber@trash.net, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 2/5] netfilter: xt extensions: use pr_<level> (2)
Date: Thu, 25 Mar 2010 15:10:12 +0100 [thread overview]
Message-ID: <4BAB6EC4.9080006@pandora.be> (raw)
In-Reply-To: <1269521809-29393-3-git-send-email-jengelh@medozas.de>
Hi Jan,
You seem to be removing all information about which module is
responsible for the message. Are you planning on a scheme to define the
pr_fmt macro for each module or did I miss something?
cheers,
Bart
Jan Engelhardt wrote:
> Supplement to 1159683ef48469de71dc26f0ee1a9c30d131cf89.
>
> Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
> ---
> net/bridge/netfilter/ebt_among.c | 15 +++++-------
> net/bridge/netfilter/ebt_limit.c | 3 +-
> net/bridge/netfilter/ebt_ulog.c | 26 +++++++++++---------
> net/bridge/netfilter/ebt_vlan.c | 36 ++++++++++------------------
> net/bridge/netfilter/ebtables.c | 5 +--
> net/ipv4/netfilter/ip_tables.c | 18 ++++++--------
> net/ipv4/netfilter/ipt_CLUSTERIP.c | 43 ++++++++++++++++++-----------------
> net/ipv4/netfilter/ipt_ECN.c | 11 +++-----
> net/ipv4/netfilter/ipt_LOG.c | 7 ++---
> net/ipv4/netfilter/ipt_MASQUERADE.c | 8 +++---
> net/ipv4/netfilter/ipt_NETMAP.c | 6 ++--
> net/ipv4/netfilter/ipt_REDIRECT.c | 6 ++--
> net/ipv4/netfilter/ipt_REJECT.c | 6 ++--
> net/ipv4/netfilter/ipt_ULOG.c | 40 +++++++++++++++-----------------
> net/ipv4/netfilter/ipt_addrtype.c | 14 +++++-----
> net/ipv4/netfilter/ipt_ecn.c | 5 +--
> net/ipv6/netfilter/ip6_tables.c | 9 +++----
> net/ipv6/netfilter/ip6t_LOG.c | 7 ++---
> net/ipv6/netfilter/ip6t_REJECT.c | 20 ++++++++--------
> net/ipv6/netfilter/ip6t_ah.c | 6 ++--
> net/ipv6/netfilter/ip6t_frag.c | 6 ++--
> net/ipv6/netfilter/ip6t_hbh.c | 6 ++--
> net/ipv6/netfilter/ip6t_rt.c | 6 ++--
> net/netfilter/xt_TCPMSS.c | 7 ++---
> net/netfilter/xt_TPROXY.c | 4 +-
> net/netfilter/xt_esp.c | 2 +-
> net/netfilter/xt_iprange.c | 1 +
> net/netfilter/xt_recent.c | 6 ++--
> net/netfilter/xt_socket.c | 5 +--
> net/netfilter/xt_time.c | 4 +-
> 30 files changed, 158 insertions(+), 180 deletions(-)
>
--
Bart De Schuymer
www.artinalgorithms.be
next prev parent reply other threads:[~2010-03-25 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 12:56 nf-next: cleanups (rd.3) Jan Engelhardt
2010-03-25 12:56 ` [PATCH 1/5] netfilter: xtables: make use of caller family rather than target family Jan Engelhardt
2010-03-25 12:56 ` [PATCH 2/5] netfilter: xt extensions: use pr_<level> (2) Jan Engelhardt
2010-03-25 13:08 ` Patrick McHardy
2010-03-25 13:20 ` Jan Engelhardt
2010-03-25 13:27 ` Patrick McHardy
2010-03-25 13:52 ` Jan Engelhardt
2010-03-25 13:59 ` Jan Engelhardt
2010-03-25 13:59 ` Patrick McHardy
2010-03-25 14:03 ` Jan Engelhardt
2010-03-25 14:10 ` Patrick McHardy
2010-03-25 14:10 ` Bart De Schuymer [this message]
2010-03-25 14:11 ` Jan Engelhardt
2010-03-25 12:56 ` [PATCH 3/5] netfilter: xtables: make use of xt_request_find_target Jan Engelhardt
2010-03-25 12:56 ` [PATCH 4/5] netfilter: xtables: consolidate code into xt_request_find_match Jan Engelhardt
2010-03-25 13:09 ` Patrick McHardy
2010-03-25 12:56 ` [PATCH 5/5] netfilter: xt_recent: allow changing ip_list_[ug]id at runtime Jan Engelhardt
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=4BAB6EC4.9080006@pandora.be \
--to=bdschuym@pandora.be \
--cc=jengelh@medozas.de \
--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 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).