From: Jeff Layton <jlayton@kernel.org>
To: john.hubbard@gmail.com
Cc: Sage Weil <sage@redhat.com>, Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
John Hubbard <jhubbard@nvidia.com>
Subject: Re: [PATCH] fs/ceph: don't return a value from void function
Date: Fri, 02 Aug 2019 12:32:37 -0400 [thread overview]
Message-ID: <89f2fdcbd007dcf6bb2b01772a17eb63459cac9d.camel@kernel.org> (raw)
In-Reply-To: <20190802010658.18150-1-jhubbard@nvidia.com>
On Thu, 2019-08-01 at 18:06 -0700, john.hubbard@gmail.com wrote:
> From: John Hubbard <jhubbard@nvidia.com>
>
> This fixes a build warning to that effect.
>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> ---
>
> Hi,
>
> I ran into this while working on unrelated changes, to
> convert ceph over to put_user_page().
>
> This patch is against the latest linux.git.
>
> thanks,
> John Hubbard
> NVIDIA
>
>
> fs/ceph/debugfs.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/fs/ceph/debugfs.c b/fs/ceph/debugfs.c
> index 2eb88ed22993..facb387c2735 100644
> --- a/fs/ceph/debugfs.c
> +++ b/fs/ceph/debugfs.c
> @@ -294,7 +294,6 @@ void ceph_fs_debugfs_init(struct ceph_fs_client *fsc)
>
> void ceph_fs_debugfs_init(struct ceph_fs_client *fsc)
> {
> - return 0;
> }
>
> void ceph_fs_debugfs_cleanup(struct ceph_fs_client *fsc)
Thanks. Merged into ceph-client/testing branch, we'll see about getting
this to Linus before v5.3 ships.
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2019-08-02 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 1:06 [PATCH] fs/ceph: don't return a value from void function john.hubbard
2019-08-02 16:32 ` 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=89f2fdcbd007dcf6bb2b01772a17eb63459cac9d.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=john.hubbard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@redhat.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