From: YueHaibing <yuehaibing@huawei.com> To: <davem@davemloft.net>, <ast@kernel.org>, <daniel@iogearbox.net>, <jakub.kicinski@netronome.com>, <hawk@kernel.org>, <john.fastabend@gmail.com> Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>, <xdp-newbies@vger.kernel.org>, <bpf@vger.kernel.org>, YueHaibing <yuehaibing@huawei.com> Subject: [PATCH net-next] xdp: Make __mem_id_disconnect static Date: Tue, 25 Jun 2019 10:31:37 +0800 [thread overview] Message-ID: <20190625023137.29272-1-yuehaibing@huawei.com> (raw) Fix sparse warning: net/core/xdp.c:88:6: warning: symbol '__mem_id_disconnect' was not declared. Should it be static? Reported-by: Hulk Robot <hulkci@huawei.com> Signed-off-by: YueHaibing <yuehaibing@huawei.com> --- net/core/xdp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/core/xdp.c b/net/core/xdp.c index b29d7b5..829377c 100644 --- a/net/core/xdp.c +++ b/net/core/xdp.c @@ -85,7 +85,7 @@ static void __xdp_mem_allocator_rcu_free(struct rcu_head *rcu) kfree(xa); } -bool __mem_id_disconnect(int id, bool force) +static bool __mem_id_disconnect(int id, bool force) { struct xdp_mem_allocator *xa; bool safe_to_remove = true; -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: YueHaibing <yuehaibing@huawei.com> To: davem@davemloft.net, ast@kernel.org, daniel@iogearbox.net, jakub.kicinski@netronome.com, hawk@kernel.org, john.fastabend@gmail.com Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, xdp-newbies@vger.kernel.org, bpf@vger.kernel.org, YueHaibing <yuehaibing@huawei.com> Subject: [PATCH net-next] xdp: Make __mem_id_disconnect static Date: Tue, 25 Jun 2019 10:31:37 +0800 [thread overview] Message-ID: <20190625023137.29272-1-yuehaibing@huawei.com> (raw) Fix sparse warning: net/core/xdp.c:88:6: warning: symbol '__mem_id_disconnect' was not declared. Should it be static? Reported-by: Hulk Robot <hulkci@huawei.com> Signed-off-by: YueHaibing <yuehaibing@huawei.com> --- net/core/xdp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/core/xdp.c b/net/core/xdp.c index b29d7b5..829377c 100644 --- a/net/core/xdp.c +++ b/net/core/xdp.c @@ -85,7 +85,7 @@ static void __xdp_mem_allocator_rcu_free(struct rcu_head *rcu) kfree(xa); } -bool __mem_id_disconnect(int id, bool force) +static bool __mem_id_disconnect(int id, bool force) { struct xdp_mem_allocator *xa; bool safe_to_remove = true; -- 2.7.4
next reply other threads:[~2019-06-25 2:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-25 2:31 YueHaibing [this message] 2019-06-25 2:31 ` [PATCH net-next] xdp: Make __mem_id_disconnect static YueHaibing 2019-06-25 9:21 ` Jesper Dangaard Brouer 2019-06-25 9:21 ` Jesper Dangaard Brouer 2019-06-25 22:23 ` Song Liu 2019-06-26 14:33 ` Daniel Borkmann
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=20190625023137.29272-1-yuehaibing@huawei.com \ --to=yuehaibing@huawei.com \ --cc=ast@kernel.org \ --cc=bpf@vger.kernel.org \ --cc=daniel@iogearbox.net \ --cc=davem@davemloft.net \ --cc=hawk@kernel.org \ --cc=jakub.kicinski@netronome.com \ --cc=john.fastabend@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=xdp-newbies@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.