From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 3/3] Misc cleanups
Date: Mon, 11 Jun 2007 16:30:34 +0200 [thread overview]
Message-ID: <466D5C8A.5000400@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0706042114190.20829@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> Removes redundant parentheses and braces.
> (And add one pair in a xt_tcpudp.c macro.)
Applied, even though I'm not sure if the risk warants the cleanup.
I tried to carefully review all changes, I trust you did the same.
> @@ -180,11 +180,10 @@ static void ipt_ulog_packet(unsigned int
>
> /* calculate the size of the skb needed */
> if ((loginfo->copy_range == 0) ||
> - (loginfo->copy_range > skb->len)) {
> + (loginfo->copy_range > skb->len))
I removed the unnecessary parentheses here as well.
> --- linux-2.6.22-rc3-git6.orig/net/ipv4/netfilter/ipt_recent.c
> +++ linux-2.6.22-rc3-git6/net/ipv4/netfilter/ipt_recent.c
> @@ -163,10 +163,9 @@ static void recent_table_flush(struct re
> struct recent_entry *e, *next;
> unsigned int i;
>
> - for (i = 0; i < ip_list_hash_size; i++) {
> + for (i = 0; i < ip_list_hash_size; i++)
> list_for_each_entry_safe(e, next, &t->iphash[i], list)
> recent_entry_remove(t, e);
> - }
Mhh .. some people prefer to have braces here. We don't do it
consistently (not even in the same file), so OK.
next prev parent reply other threads:[~2007-06-11 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 19:09 [PATCH 0/3] Misc cleanups Jan Engelhardt
2007-06-04 19:11 ` [PATCH 1/3] " Jan Engelhardt
2007-06-11 14:17 ` Patrick McHardy
2007-06-11 14:31 ` Jan Engelhardt
2007-06-11 14:34 ` Patrick McHardy
2007-06-04 19:13 ` [PATCH 2/3] " Jan Engelhardt
2007-06-11 14:18 ` Patrick McHardy
2007-06-04 19:14 ` [PATCH 3/3] " Jan Engelhardt
2007-06-11 14:30 ` Patrick McHardy [this message]
2007-06-06 16:11 ` [PATCH 0/3] " Patrick McHardy
2007-06-07 6:56 ` Jan Engelhardt
2007-06-07 8:26 ` 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=466D5C8A.5000400@trash.net \
--to=kaber@trash.net \
--cc=jengelh@linux01.gwdg.de \
--cc=netfilter-devel@lists.netfilter.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.