From: Pablo Neira Ayuso <pablo@netfilter.org>
To: fgao@ikuai8.com
Cc: kaber@trash.net, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, gfree.wind@gmail.com
Subject: Re: [PATCH v3 net-next 1/2] netfilter: gre: Use consistent GRE_* macros instead of ones defined by netfilter.
Date: Wed, 7 Sep 2016 10:47:39 +0200 [thread overview]
Message-ID: <20160907084739.GA3842@salvia> (raw)
In-Reply-To: <1472137691-24822-1-git-send-email-fgao@ikuai8.com>
On Thu, Aug 25, 2016 at 11:08:11PM +0800, fgao@ikuai8.com wrote:
> From: Gao Feng <fgao@ikuai8.com>
>
> There are already some GRE_* macros in kernel, so it is unnecessary
> to define these macros. And remove some useless macros
Applied, thanks.
prev parent reply other threads:[~2016-09-07 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 15:08 [PATCH v3 net-next 1/2] netfilter: gre: Use consistent GRE_* macros instead of ones defined by netfilter fgao
2016-09-07 8:47 ` 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=20160907084739.GA3842@salvia \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=fgao@ikuai8.com \
--cc=gfree.wind@gmail.com \
--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).