From: Jan Kara <jack@suse.cz>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: Jan Kara <jack@suse.cz>, Al Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: isofs: One check less in isofs_read_inode() after error detection
Date: Tue, 22 Aug 2017 10:48:15 +0000 [thread overview]
Message-ID: <20170822104815.GJ4909@quack2.suse.cz> (raw)
In-Reply-To: <d2516ec9-5231-bbeb-3534-f0bd6992478c@users.sourceforge.net>
On Mon 21-08-17 16:18:14, SF Markus Elfring wrote:
> > I agree that
> >
> > fail:
> > goto out;
> >
> > in the original code is awkward and we can get rid of it.
>
> How would you like to change this place instead?
Just do 'goto out' directly.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-08-22 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 7:14 [PATCH 0/4] ISOFS: Adjustments for three function implementations SF Markus Elfring
2017-08-19 7:15 ` [PATCH 1/4] isofs: Delete an error message for a failed memory allocation in isofs_read_inode() SF Markus Elfring
2017-08-21 14:06 ` Jan Kara
2017-08-19 7:17 ` [PATCH 2/4] isofs: Adjust four checks for null pointers SF Markus Elfring
2017-08-21 14:06 ` Jan Kara
2017-08-19 7:18 ` [PATCH 3/4] isofs: One check less in isofs_read_inode() after error detection SF Markus Elfring
2017-08-21 14:11 ` Jan Kara
2017-08-21 14:18 ` SF Markus Elfring
2017-08-22 10:48 ` Jan Kara [this message]
2017-08-19 7:19 ` [PATCH 4/4] isofs: Delete an unnecessary variable initialisation in isofs_read_inode() SF Markus Elfring
2017-08-21 14:12 ` Jan Kara
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=20170822104815.GJ4909@quack2.suse.cz \
--to=jack@suse.cz \
--cc=dhowells@redhat.com \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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