From: Jakub Kicinski <kuba@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Roopa Prabhu <roopa@nvidia.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Eric Dumazet <edumazet@google.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Eelco Chaudron <echaudro@redhat.com>,
Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vxlan: fix returnvar.cocci warnings
Date: Mon, 21 Mar 2022 12:16:02 -0700 [thread overview]
Message-ID: <20220321121602.11b896e4@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20220321154456.GA30106@e0e7ddfdfbf7>
On Mon, 21 Mar 2022 23:44:57 +0800 kernel test robot wrote:
> From: kernel test robot <lkp@intel.com>
>
> drivers/net/vxlan/vxlan_core.c:2962:5-8: Unneeded variable: "ret". Return "0" on line 2971
>
>
> Remove unneeded variable used to store return value.
>
> Generated by: scripts/coccinelle/misc/returnvar.cocci
>
> Fixes: f9c4bb0b245c ("vxlan: vni filtering support on collect metadata device")
> CC: Roopa Prabhu <roopa@nvidia.com>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: kernel test robot <lkp@intel.com>
Your tree is stale, this looks exactly like commit e58bc864630f
("drivers: vxlan: fix returnvar.cocci warning") merged on March 8th.
prev parent reply other threads:[~2022-03-21 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 15:46 [linux-next:master 8808/13988] drivers/net/vxlan/vxlan_core.c:2962:5-8: Unneeded variable: "ret". Return "0" on line 2971 kernel test robot
2022-03-21 15:44 ` [PATCH] vxlan: fix returnvar.cocci warnings kernel test robot
2022-03-21 19:16 ` Jakub Kicinski [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=20220321121602.11b896e4@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@nvidia.com \
/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