From: Casey Schaufler <casey@schaufler-ca.com>
To: kbuild test robot <fengguang.wu@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: kbuild-all@01.org, James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysfs: fix simple_return.cocci warnings
Date: Wed, 22 Jul 2015 12:38:00 -0700 [thread overview]
Message-ID: <55AFF118.2050302@schaufler-ca.com> (raw)
In-Reply-To: <20150623234107.GA102996@lkp-sb04>
On 6/23/2015 4:41 PM, kbuild test robot wrote:
> security/smack/smackfs.c:2251:1-4: WARNING: end returns can be simpified and declaration on line 2250 can be dropped
>
> Simplify a trivial if-return sequence. Possibly combine with a
> preceding function call.
>
> Generated by: scripts/coccinelle/misc/simple_return.cocci
>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Acked-by: Casey Schaufler <casey@schaufler-ca.com>
Applied to https://github.com/cschaufler/smack-next.git#smack-for-4.3
> ---
>
> smackfs.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> --- a/security/smack/smackfs.c
> +++ b/security/smack/smackfs.c
> @@ -2247,11 +2247,7 @@ static const struct file_operations smk_
> */
> static int smk_init_sysfs(void)
> {
> - int err;
> - err = sysfs_create_mount_point(fs_kobj, "smackfs");
> - if (err)
> - return err;
> - return 0;
> + return sysfs_create_mount_point(fs_kobj, "smackfs");
> }
>
> /**
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2015-07-22 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201506240705.vNc0oiCA%fengguang.wu@intel.com>
2015-06-23 23:41 ` kbuild test robot
2015-06-25 13:13 ` Serge E. Hallyn
2015-07-22 19:38 ` Casey Schaufler [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=55AFF118.2050302@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=ebiederm@xmission.com \
--cc=fengguang.wu@intel.com \
--cc=james.l.morris@oracle.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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
Powered by JetHome