From: Eric Sandeen <sandeen@redhat.com>
To: Brian Foster <bfoster@redhat.com>, Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH V2] xfs: change some error-less functions to void types
Date: Thu, 2 May 2019 09:44:59 -0500 [thread overview]
Message-ID: <c73c4e8f-dafb-d216-3af8-28bf1f1aac60@redhat.com> (raw)
In-Reply-To: <20190502121741.GB22716@bfoster>
On 5/2/19 7:17 AM, Brian Foster wrote:
>> - return 0;
>> + return;
> No need for return statements at the end of void functions. With that
> fixed up (here and throughout the rest of the patch):
>
> Reviewed-by: Brian Foster <bfoster@redhat.com>
>
Oh, hah. IR smart. (was on autopilot...) I'll send V3.
-Eric
next prev parent reply other threads:[~2019-05-02 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 15:55 [PATCH] xfs: change some error-less functions to void types Eric Sandeen
2019-05-01 22:16 ` Dave Chinner
2019-05-01 22:20 ` [PATCH V2] " Eric Sandeen
2019-05-01 23:49 ` Dave Chinner
2019-05-02 12:17 ` Brian Foster
2019-05-02 14:44 ` Eric Sandeen [this message]
2019-05-02 14:50 ` [PATCH V3] " Eric Sandeen
2019-05-02 14:59 ` [PATCH V4] " Eric Sandeen
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=c73c4e8f-dafb-d216-3af8-28bf1f1aac60@redhat.com \
--to=sandeen@redhat.com \
--cc=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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