From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Bill O'Donnell <billodo@redhat.com>,
Krzysztof Blaszkowski <kb@sysmikro.com.pl>
Subject: Re: [PATCH] freevxfs: Convert freevxfs to the new mount API.
Date: Mon, 4 Mar 2024 14:02:43 +0100 [thread overview]
Message-ID: <20240304-grasen-fehlen-6ca8c1bd6f8e@brauner> (raw)
In-Reply-To: <b0d1a423-4b8e-4bc1-a021-a1078aee915f@redhat.com>
On Fri, 01 Mar 2024 17:04:31 -0600, Eric Sandeen wrote:
> Convert the freevxfs filesystem to the new mount API.
>
>
@Krzysztof, sorry I had to butcher your last name. But git send-email
keeps breaking the mail headers for me here. This isn't the first time
this has happened but I haven't found a remedy for this yet.
---
Applied to the vfs.mount.api branch of the vfs/vfs.git tree.
Patches in the vfs.mount.api 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.mount.api
[1/1] freevxfs: Convert freevxfs to the new mount API.
https://git.kernel.org/vfs/vfs/c/f65b9daeb55b
next prev parent reply other threads:[~2024-03-04 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 23:04 [PATCH] freevxfs: Convert freevxfs to the new mount API Eric Sandeen
2024-03-04 13:02 ` Christian Brauner [this message]
2024-03-05 13:47 ` Christoph Hellwig
2024-03-05 16:18 ` 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=20240304-grasen-fehlen-6ca8c1bd6f8e@brauner \
--to=brauner@kernel.org \
--cc=billodo@redhat.com \
--cc=hch@infradead.org \
--cc=kb@sysmikro.com.pl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.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