From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [cifs:for-next 9/15] fs/cifs/fs_context.c:238:5-7: Unneeded variable: "rc". Return "0" on line 261
Date: Sat, 12 Dec 2020 08:47:57 +0800 [thread overview]
Message-ID: <202012120814.pRiAmhm4-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-cifs(a)vger.kernel.org
CC: samba-technical(a)lists.samba.org
TO: Ronnie Sahlberg <lsahlber@redhat.com>
CC: Steve French <stfrench@microsoft.com>
tree: git://git.samba.org/sfrench/cifs-2.6.git for-next
head: 2dc7338d009dd9e5986121b2eae0178082eed5a1
commit: 8dd343e732466a0dd040898bddefd4e1c556dd10 [9/15] cifs: rename dup_vol to smb3_fs_context_dup and move it into fs_context.c
:::::: branch date: 3 hours ago
:::::: commit date: 3 hours ago
config: i386-randconfig-c001-20201209 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>
"coccinelle warnings: (new ones prefixed by >>)"
>> fs/cifs/fs_context.c:238:5-7: Unneeded variable: "rc". Return "0" on line 261
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 39075 bytes --]
next reply other threads:[~2020-12-12 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 0:47 kernel test robot [this message]
2020-12-12 0:47 ` [PATCH] cifs: fix returnvar.cocci warnings kernel test robot
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=202012120814.pRiAmhm4-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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 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.