From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Liping Zhang <zlpwmdx@163.com>
Cc: kaber@trash.net, davem@davemloft.net,
netfilter-devel@vger.kernel.org,
Liping Zhang <liping.zhang@spreadtrum.com>
Subject: Re: [PATCH] netfilter: ip6t_SYNPROXY: remove magic number
Date: Mon, 28 Mar 2016 13:00:44 +0200 [thread overview]
Message-ID: <20160328110044.GA2982@salvia> (raw)
In-Reply-To: <1458743356-4045-1-git-send-email-zlpwmdx@163.com>
On Wed, Mar 23, 2016 at 10:29:16PM +0800, Liping Zhang wrote:
> From: Liping Zhang <liping.zhang@spreadtrum.com>
>
> Replace '64' with the per-net ipv6_devconf_all's hop_limit when
> building the ipv6 header.
Could you resend a patch based on top of:
netfilter: ipv4: fix NULL dereference
Thanks.
prev parent reply other threads:[~2016-03-28 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 14:29 [PATCH] netfilter: ip6t_SYNPROXY: remove magic number Liping Zhang
2016-03-28 11:00 ` Pablo Neira Ayuso [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=20160328110044.GA2982@salvia \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=liping.zhang@spreadtrum.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=zlpwmdx@163.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).