From: kernel test robot <lkp@intel.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [pcmoore-lsm:next-queue 11/18] checkpatch: WARNING: else is not generally useful after a break or return
Date: Sat, 14 Oct 2023 15:54:37 +0800 [thread overview]
Message-ID: <202310141552.P7ptSUPL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git next-queue
head: 44cc05348273c0e26a9093fe5b882f3ab5203424
commit: 357595fcb7c7dcd515c66e92813d53fc8074809a [11/18] LSM: syscalls for current process attributes
reproduce: (https://download.01.org/0day-ci/archive/20231014/202310141552.P7ptSUPL-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310141552.P7ptSUPL-lkp@intel.com/
# many are suggestions rather than must-fix
WARNING:UNNECESSARY_ELSE: else is not generally useful after a break or return
#449: FILE: security/security.c:3917:
+ return rc;
+ else
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-14 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202310141552.P7ptSUPL-lkp@intel.com \
--to=lkp@intel.com \
--cc=casey@schaufler-ca.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.