From: Chuck Lever <chuck.lever@oracle.com>
To: Benjamin Coddington <bcodding@hammerspace.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v4 0/3] Allow knfsd to use atomic_open()
Date: Thu, 4 Dec 2025 12:38:38 -0500 [thread overview]
Message-ID: <10093dbe-449c-4bb3-bdaf-6264292e0c66@oracle.com> (raw)
In-Reply-To: <EF15582A-A753-46F0-8011-E4EBFAFB33C7@hammerspace.com>
On 12/4/25 12:36 PM, Benjamin Coddington wrote:
>> I assume that since you sent To: Al/Christian, they would be taking this
>> through one of the VFS trees; hence my R-b.
> Thanks for that - usually there's some discussion on which tree would take
> this which I didn't see yet. Hope Al/Christian will pick it up.
There hasn't been any discussion, so you didn't miss anything. I just
assumed, based on the To: line.
I'm happy to take these if Al & Christian feel that's more appropriate.
--
Chuck Lever
next prev parent reply other threads:[~2025-12-04 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 16:02 Benjamin Coddington
2025-11-27 16:02 ` [PATCH v4 1/3] VFS: move dentry_create() from fs/open.c to fs/namei.c Benjamin Coddington
2025-11-27 16:02 ` [PATCH v4 2/3] VFS: Prepare atomic_open() for dentry_create() Benjamin Coddington
2025-11-27 16:02 ` [PATCH v4 3/3] VFS/knfsd: Teach dentry_create() to use atomic_open() Benjamin Coddington
2025-12-04 15:05 ` [PATCH v4 0/3] Allow knfsd " Benjamin Coddington
2025-12-04 17:33 ` Chuck Lever
2025-12-04 17:36 ` Benjamin Coddington
2025-12-04 17:38 ` Chuck Lever [this message]
2025-12-05 9:31 ` Christian Brauner
2025-12-05 12:33 ` Benjamin Coddington
2025-12-05 9:30 ` 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=10093dbe-449c-4bb3-bdaf-6264292e0c66@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bcodding@hammerspace.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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
all inboxes | Powered by JetHome®