All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiubo Li <xiubli@redhat.com>
To: Jeff Layton <jlayton@kernel.org>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] ceph: make ceph_queue_cap_snap static
Date: Wed, 19 May 2021 08:52:51 +0800	[thread overview]
Message-ID: <115e9937-bfa1-d498-10e9-4f187e2ad323@redhat.com> (raw)
In-Reply-To: <20210518213628.119867-1-jlayton@kernel.org>


On 5/19/21 5:36 AM, Jeff Layton wrote:
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
>   fs/ceph/snap.c  | 2 +-
>   fs/ceph/super.h | 1 -
>   2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/ceph/snap.c b/fs/ceph/snap.c
> index 4ce18055d931..44b380a53727 100644
> --- a/fs/ceph/snap.c
> +++ b/fs/ceph/snap.c
> @@ -460,7 +460,7 @@ static bool has_new_snaps(struct ceph_snap_context *o,
>    * Caller must hold snap_rwsem for read (i.e., the realm topology won't
>    * change).
>    */
> -void ceph_queue_cap_snap(struct ceph_inode_info *ci)
> +static void ceph_queue_cap_snap(struct ceph_inode_info *ci)
>   {
>   	struct inode *inode = &ci->vfs_inode;
>   	struct ceph_cap_snap *capsnap;
> diff --git a/fs/ceph/super.h b/fs/ceph/super.h
> index db80d89556b1..12d30153e4ca 100644
> --- a/fs/ceph/super.h
> +++ b/fs/ceph/super.h
> @@ -931,7 +931,6 @@ extern int ceph_update_snap_trace(struct ceph_mds_client *m,
>   extern void ceph_handle_snap(struct ceph_mds_client *mdsc,
>   			     struct ceph_mds_session *session,
>   			     struct ceph_msg *msg);
> -extern void ceph_queue_cap_snap(struct ceph_inode_info *ci);
>   extern int __ceph_finish_cap_snap(struct ceph_inode_info *ci,
>   				  struct ceph_cap_snap *capsnap);
>   extern void ceph_cleanup_empty_realms(struct ceph_mds_client *mdsc);

Reviewed-by: Xiubo Li <xiubli@redhat.com>



      reply	other threads:[~2021-05-19  0:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 21:36 [PATCH] ceph: make ceph_queue_cap_snap static Jeff Layton
2021-05-19  0:52 ` Xiubo Li [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=115e9937-bfa1-d498-10e9-4f187e2ad323@redhat.com \
    --to=xiubli@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jlayton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.