From: Christian Brauner <brauner@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
Marc Dionne <marc.dionne@auristor.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] afs: Add support for RENAME_NOREPLACE and RENAME_EXCHANGE
Date: Thu, 25 Sep 2025 09:19:40 +0200 [thread overview]
Message-ID: <20250925-zudem-pause-b4275afb1926@brauner> (raw)
In-Reply-To: <740476.1758718189@warthog.procyon.org.uk>
On Wed, 24 Sep 2025 13:49:49 +0100, David Howells wrote:
> Add support for RENAME_NOREPLACE and RENAME_EXCHANGE, if the server
> supports them.
>
> The default is translated to YFS.Rename_Replace, falling back to
> YFS.Rename; RENAME_NOREPLACE is translated to YFS.Rename_NoReplace and
> RENAME_EXCHANGE to YFS.Rename_Exchange, both of which fall back to
> reporting EINVAL.
>
> [...]
Applied to the vfs-6.18.afs branch of the vfs/vfs.git tree.
Patches in the vfs-6.18.afs branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.18.afs
[1/1] afs: Add support for RENAME_NOREPLACE and RENAME_EXCHANGE
https://git.kernel.org/vfs/vfs/c/a19239ba1452
prev parent reply other threads:[~2025-09-25 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 12:49 [PATCH v4] afs: Add support for RENAME_NOREPLACE and RENAME_EXCHANGE David Howells
2025-09-25 7:19 ` Christian Brauner [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=20250925-zudem-pause-b4275afb1926@brauner \
--to=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.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;
as well as URLs for NNTP newsgroup(s).