From: David Miller <davem@davemloft.net>
To: tklauser@distanz.ch
Cc: netdev@vger.kernel.org, ast@kernel.org, kafai@fb.com
Subject: Re: [PATCH net-next] bpf: Remove unused but set variable in __bpf_lru_list_shrink_inactive()
Date: Tue, 10 Jan 2017 21:01:37 -0500 (EST) [thread overview]
Message-ID: <20170110.210137.849302729948766638.davem@davemloft.net> (raw)
In-Reply-To: <20170110140207.26480-1-tklauser@distanz.ch>
From: Tobias Klauser <tklauser@distanz.ch>
Date: Tue, 10 Jan 2017 15:02:07 +0100
> Remove the unused but set variable 'first_node' in
> __bpf_lru_list_shrink_inactive() to fix the following GCC warning when
> building with 'W=1':
>
> kernel/bpf/bpf_lru_list.c:216:41: warning: variable ‘first_node’ set but not used [-Wunused-but-set-variable]
>
> Cc: Martin KaFai Lau <kafai@fb.com>
> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Applied.
prev parent reply other threads:[~2017-01-11 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 14:02 [PATCH net-next] bpf: Remove unused but set variable in __bpf_lru_list_shrink_inactive() Tobias Klauser
2017-01-11 0:25 ` Alexei Starovoitov
2017-01-11 0:57 ` Martin KaFai Lau
2017-01-11 0:58 ` Martin KaFai Lau
2017-01-11 2:01 ` David Miller [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=20170110.210137.849302729948766638.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=tklauser@distanz.ch \
/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).