From: Jeff Layton <jlayton@kernel.org>
To: Luis Henriques <lhenriques@suse.de>,
David Laight <David.Laight@ACULAB.COM>
Cc: Ilya Dryomov <idryomov@gmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ceph: remove unnecessary return in switch statement
Date: Sun, 16 Aug 2020 10:00:46 -0400 [thread overview]
Message-ID: <116297e8efab260d8dd61e9dcc36aa3414e9b1d9.camel@kernel.org> (raw)
In-Reply-To: <877du1h7db.fsf@suse.de>
On Fri, 2020-08-14 at 11:03 +0100, Luis Henriques wrote:
> David Laight <David.Laight@ACULAB.COM> writes:
>
> > From: Luis Henriques
> > > Sent: 14 August 2020 10:38
> > >
> > > Since there's a return immediately after the 'break', there's no need for
> > > this extra 'return' in the S_IFDIR case.
> > >
> > > Signed-off-by: Luis Henriques <lhenriques@suse.de>
> > > ---
> > > fs/ceph/file.c | 2 --
> > > 1 file changed, 2 deletions(-)
> > >
> > > diff --git a/fs/ceph/file.c b/fs/ceph/file.c
> > > index d51c3f2fdca0..04ab99c0223a 100644
> > > --- a/fs/ceph/file.c
> > > +++ b/fs/ceph/file.c
> > > @@ -256,8 +256,6 @@ static int ceph_init_file(struct inode *inode, struct file *file, int fmode)
> > > case S_IFDIR:
> > > ret = ceph_init_file_info(inode, file, fmode,
> > > S_ISDIR(inode->i_mode));
> > > - if (ret)
> > > - return ret;
> > > break;
> > >
> > > case S_IFLNK:
> >
> > I'd move the other way and just do:
> > return ceph_init_file_info(...);
>
> Sure, that would work too, although my preference would be to have a
> single function exit point. But I'll leave that decision to Jeff :-)
>
I think I agree with Luis here (though it's really a bit subjective). I
don't think it'll matter much to the compiled result either way, and
that will probably be better if this function grows in complexity.
I'll plan to merge this patch in the next day or so.
Thanks!
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2020-08-16 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 9:38 Luis Henriques
2020-08-14 9:52 ` David Laight
2020-08-14 10:03 ` Luis Henriques
2020-08-16 14:00 ` Jeff Layton [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=116297e8efab260d8dd61e9dcc36aa3414e9b1d9.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=David.Laight@ACULAB.COM \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=lhenriques@suse.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome