From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfilter: use PTR_RET
Date: Mon, 29 Oct 2012 10:03:47 +0100 [thread overview]
Message-ID: <20121029090347.GA10521@1984> (raw)
In-Reply-To: <20121029004044.GA12982@localhost>
On Mon, Oct 29, 2012 at 08:40:44AM +0800, Fengguang Wu wrote:
> Use PTR_RET rather than if(IS_ERR(...)) + PTR_ERR
>
> Generated by: coccinelle/api/ptr_ret.cocci
Applied, thanks.
I have collapsed this patch and the one for ipv6/iptable_nat.c. They
are pretty small and description is the same.
next prev parent reply other threads:[~2012-10-29 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 0:40 [PATCH] netfilter: use PTR_RET Fengguang Wu
2012-10-29 0:55 ` [PATCH] netfilter: ipv6: " Fengguang Wu
2012-10-29 9:03 ` Pablo Neira Ayuso [this message]
2012-10-29 9:13 ` [PATCH] netfilter: " Fengguang Wu
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=20121029090347.GA10521@1984 \
--to=pablo@netfilter.org \
--cc=fengguang.wu@intel.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--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).