From: Pablo Neira Ayuso <pablo@netfilter.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org
Subject: Re: [RFC PATCH nf-next] netfilter: core: __nf_unregister_net_hook() can be static
Date: Thu, 21 Dec 2017 00:18:10 +0100 [thread overview]
Message-ID: <20171220231810.owqgq2cs4ataskry@salvia> (raw)
In-Reply-To: <20171219172540.GA56682@lkp-sb05>
On Wed, Dec 20, 2017 at 01:25:40AM +0800, kbuild test robot wrote:
>
> Fixes: ac119d8cd089 ("netfilter: core: support for NFPROTO_INET hook registration")
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
I have folded this patch to my patchset, thanks.
prev parent reply other threads:[~2017-12-20 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 17:25 [nf-next:for-net-next3 28/40] net/netfilter/core.c:403:6: sparse: symbol '__nf_unregister_net_hook' was not declared. Should it be static? kbuild test robot
2017-12-19 17:25 ` [RFC PATCH nf-next] netfilter: core: __nf_unregister_net_hook() can be static kbuild test robot
2017-12-20 23:18 ` 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=20171220231810.owqgq2cs4ataskry@salvia \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.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).