From: "J . Bruce Fields" <bfields@fieldses.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Jeff Layton <jlayton@kernel.org>,
Jiri Kosina <trivial@kernel.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [trivial] nfsd: Spelling s/EACCESS/EACCES/
Date: Fri, 31 May 2019 09:36:49 -0400 [thread overview]
Message-ID: <20190531133649.GA1251@fieldses.org> (raw)
In-Reply-To: <20190527122132.5617-1-geert+renesas@glider.be>
Thanks, applying for 5.3.--b.
On Mon, May 27, 2019 at 02:21:32PM +0200, Geert Uytterhoeven wrote:
> The correct spelling is EACCES:
>
> include/uapi/asm-generic/errno-base.h:#define EACCES 13 /* Permission denied */
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> fs/nfsd/vfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
> index fc24ee47eab51ad4..c85783e536d595de 100644
> --- a/fs/nfsd/vfs.c
> +++ b/fs/nfsd/vfs.c
> @@ -404,7 +404,7 @@ nfsd_setattr(struct svc_rqst *rqstp, struct svc_fh *fhp, struct iattr *iap,
> /*
> * If utimes(2) and friends are called with times not NULL, we should
> * not set NFSD_MAY_WRITE bit. Otherwise fh_verify->nfsd_permission
> - * will return EACCESS, when the caller's effective UID does not match
> + * will return EACCES, when the caller's effective UID does not match
> * the owner of the file, and the caller is not privileged. In this
> * situation, we should return EPERM(notify_change will return this).
> */
> --
> 2.17.1
prev parent reply other threads:[~2019-05-31 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 12:21 [PATCH] [trivial] nfsd: Spelling s/EACCESS/EACCES/ Geert Uytterhoeven
2019-05-31 13:36 ` J . Bruce Fields [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=20190531133649.GA1251@fieldses.org \
--to=bfields@fieldses.org \
--cc=geert+renesas@glider.be \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trivial@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