From: Eric Biggers <ebiggers@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: jlayton@redhat.com, amir73il@gmail.com, trondmy@hammerspace.com,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
viro@zeniv.linux.org.uk, brauner@kernel.org
Subject: Re: [PATCH v5 2/2] fs: Create a generic is_dot_dotdot() utility
Date: Wed, 24 Jan 2024 14:19:52 -0800 [thread overview]
Message-ID: <20240124221952.GE1088@sol.localdomain> (raw)
In-Reply-To: <170575907468.22911.10976023123447238559.stgit@klimt.1015granger.net>
On Sat, Jan 20, 2024 at 08:57:54AM -0500, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> De-duplicate the same functionality in several places by hoisting
> the is_dot_dotdot() utility function into linux/fs.h.
>
> Suggested-by: Amir Goldstein <amir73il@gmail.com>
> Reviewed-by: Jeff Layton <jlayton@kernel.org>
> Reviewed-by: Amir Goldstein <amir73il@gmail.com>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> fs/crypto/fname.c | 8 +-------
> fs/ecryptfs/crypto.c | 10 ----------
> fs/exportfs/expfs.c | 10 ----------
> fs/f2fs/f2fs.h | 11 -----------
> fs/namei.c | 6 ++----
> include/linux/fs.h | 11 +++++++++++
> 6 files changed, 14 insertions(+), 42 deletions(-)
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
next prev parent reply other threads:[~2024-01-24 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 13:57 [PATCH v5 0/2] fix the fallback implementation of get_name Chuck Lever
2024-01-20 13:57 ` [PATCH v5 1/2] exportfs: fix the fallback implementation of the get_name export operation Chuck Lever
2024-01-20 13:57 ` [PATCH v5 2/2] fs: Create a generic is_dot_dotdot() utility Chuck Lever
2024-01-24 22:19 ` Eric Biggers [this message]
2024-01-23 15:51 ` [PATCH v5 0/2] fix the fallback implementation of get_name Christian Brauner
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=20240124221952.GE1088@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.com \
--cc=viro@zeniv.linux.org.uk \
/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