From: kbuild test robot <lkp@intel.com>
To: Tom Herbert <tom@quantonium.net>
Cc: kbuild-all@01.org, davem@davemloft.net, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, rohit@quantonium.net,
Tom Herbert <tom@quantonium.net>
Subject: [RFC PATCH] ila: ila_notify() can be static
Date: Sun, 17 Dec 2017 06:18:48 +0800 [thread overview]
Message-ID: <20171216221848.GA16562@lkp-sb04> (raw)
In-Reply-To: <20171215182800.10248-7-tom@quantonium.net>
Fixes: bdefe11e33bb ("ila: Route notify")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
ila_lwt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/ipv6/ila/ila_lwt.c b/net/ipv6/ila/ila_lwt.c
index 303c91e..fbf6273 100644
--- a/net/ipv6/ila/ila_lwt.c
+++ b/net/ipv6/ila/ila_lwt.c
@@ -51,7 +51,7 @@ static size_t ila_rslv_msgsize(void)
return len;
}
-void ila_notify(struct net *net, struct sk_buff *skb, struct ila_lwt *lwt)
+static void ila_notify(struct net *net, struct sk_buff *skb, struct ila_lwt *lwt)
{
struct ipv6hdr *ip6h = ipv6_hdr(skb);
int flags = NLM_F_MULTI;
next prev parent reply other threads:[~2017-12-16 22:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 18:27 [PATCH v4 net-next 0/6] net: ILA notification mechanism and fixes Tom Herbert
2017-12-15 18:27 ` [PATCH v4 net-next 1/6] lwt: Add net to build_state argument Tom Herbert
2017-12-19 15:47 ` Roopa Prabhu
2017-12-15 18:27 ` [PATCH v4 net-next 2/6] ila: Fix use of rhashtable walk in ila_xlat.c Tom Herbert
2017-12-15 18:27 ` [PATCH v4 net-next 3/6] ila: Call library function alloc_bucket_locks Tom Herbert
2017-12-16 20:47 ` kbuild test robot
2017-12-15 18:27 ` [PATCH v4 net-next 4/6] ila: create main ila source file Tom Herbert
2017-12-15 18:27 ` [PATCH v4 net-next 5/6] ila: Flush netlink command to clear xlat table Tom Herbert
2017-12-15 18:28 ` [PATCH v4 net-next 6/6] ila: Route notify Tom Herbert
2017-12-16 22:18 ` kbuild test robot [this message]
2017-12-16 22:18 ` kbuild test robot
2017-12-19 16:28 ` Roopa Prabhu
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=20171216221848.GA16562@lkp-sb04 \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=rohit@quantonium.net \
--cc=roopa@cumulusnetworks.com \
--cc=tom@quantonium.net \
/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).