From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 3/3] NFSD: Clean up header guards in fs/nfsd/xdr.h
Date: Wed, 19 Aug 2026 06:52:00 -0400 [thread overview]
Message-ID: <dab1f7a1c5c349eda6539c1059bd2364f7ed718c.camel@kernel.org> (raw)
In-Reply-To: <20260818140035.12740-3-cel@kernel.org>
On Tue, 2026-08-18 at 10:00 -0400, Chuck Lever wrote:
> Make the header guards less ambiguous about their provenance.
>
> Signed-off-by: Chuck Lever <cel@kernel.org>
> ---
> fs/nfsd/xdr.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/nfsd/xdr.h b/fs/nfsd/xdr.h
> index df540c940cef..52660b9f8dde 100644
> --- a/fs/nfsd/xdr.h
> +++ b/fs/nfsd/xdr.h
> @@ -1,8 +1,8 @@
> /* SPDX-License-Identifier: GPL-2.0 */
> /* XDR types for nfsd. This is mainly a typing exercise. */
>
> -#ifndef LINUX_NFSD_H
> -#define LINUX_NFSD_H
> +#ifndef _LINUX_NFSD_XDR_H
> +#define _LINUX_NFSD_XDR_H
>
> #include <linux/vfs.h>
> #include "nfsd.h"
> @@ -175,4 +175,4 @@ bool svcxdr_encode_stat(struct xdr_stream *xdr, __be32 status);
> bool svcxdr_encode_fattr(struct svc_rqst *rqstp, struct xdr_stream *xdr,
> const struct svc_fh *fhp, const struct kstat *stat);
>
> -#endif /* LINUX_NFSD_H */
> +#endif /* _LINUX_NFSD_XDR_H */
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-08-19 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 14:00 [PATCH 1/3] NFSD: Move the nfs3.h include out of nfsd.h Chuck Lever
2026-08-18 14:00 ` [PATCH 2/3] NFSD: Include <linux/nfs_fh.h> where struct nfs_fh is used Chuck Lever
2026-08-19 10:51 ` Jeff Layton
2026-08-18 14:00 ` [PATCH 3/3] NFSD: Clean up header guards in fs/nfsd/xdr.h Chuck Lever
2026-08-19 10:52 ` Jeff Layton [this message]
2026-08-19 10:51 ` [PATCH 1/3] NFSD: Move the nfs3.h include out of nfsd.h Jeff Layton
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=dab1f7a1c5c349eda6539c1059bd2364f7ed718c.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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