From: Chuck Lever III <chuck.lever@oracle.com>
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: Jeff Layton <jlayton@kernel.org>, Christoph Hellwig <hch@lst.de>,
Bruce Fields <bfields@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nfsd: remove nfsd4_prepare_cb_recall() declaration
Date: Fri, 9 Sep 2022 15:32:22 +0000 [thread overview]
Message-ID: <D2116287-4A49-4CED-87C4-AC447901385F@oracle.com> (raw)
In-Reply-To: <20220909065910.1157954-1-cuigaosheng1@huawei.com>
> On Sep 9, 2022, at 2:59 AM, Gaosheng Cui <cuigaosheng1@huawei.com> wrote:
>
> nfsd4_prepare_cb_recall() has been removed since
> commit 0162ac2b978e ("nfsd: introduce nfsd4_callback_ops"),
> so remove it.
>
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
Applied to for-next (6.1). Thanks!
> ---
> fs/nfsd/state.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/fs/nfsd/state.h b/fs/nfsd/state.h
> index 5d28beb290fe..4155be65d806 100644
> --- a/fs/nfsd/state.h
> +++ b/fs/nfsd/state.h
> @@ -697,7 +697,6 @@ extern int nfsd4_create_callback_queue(void);
> extern void nfsd4_destroy_callback_queue(void);
> extern void nfsd4_shutdown_callback(struct nfs4_client *);
> extern void nfsd4_shutdown_copy(struct nfs4_client *clp);
> -extern void nfsd4_prepare_cb_recall(struct nfs4_delegation *dp);
> extern struct nfs4_client_reclaim *nfs4_client_to_reclaim(struct xdr_netobj name,
> struct xdr_netobj princhash, struct nfsd_net *nn);
> extern bool nfs4_has_reclaimed_state(struct xdr_netobj name, struct nfsd_net *nn);
> --
> 2.25.1
>
--
Chuck Lever
prev parent reply other threads:[~2022-09-09 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 6:59 Gaosheng Cui
2022-09-09 15:32 ` Chuck Lever III [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=D2116287-4A49-4CED-87C4-AC447901385F@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bfields@redhat.com \
--cc=cuigaosheng1@huawei.com \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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
all inboxes | Powered by JetHome®