From: Christian Brauner <brauner@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Christian Brauner <brauner@kernel.org>,
NeilBrown <neilb@ownmail.net>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3 0/4] cleanup block-style layouts exports
Date: Mon, 11 May 2026 11:15:19 +0200 [thread overview]
Message-ID: <20260511-zombie-habilitation-08bc00f1a404@brauner> (raw)
In-Reply-To: <20260423181854.743150-1-cel@kernel.org>
On Thu, 23 Apr 2026 14:18:50 -0400, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> Following up on https://lore.kernel.org/linux-nfs/20260401144059.160746-1-hch@lst.de/#r
>
> Here is the current version of Christoph's patches that are in
> nfsd-testing. Christian prefers to see them taken through the VFS
> tree. Once the patches are applied there, I will rebase nfsd-next
> and nfsd-testing on that tree and drop these.
>
> [...]
The branch is stable in case anyone wants to rely on it.
---
Applied to the vfs-7.2.exportfs branch of the vfs/vfs.git tree.
Patches in the vfs-7.2.exportfs 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-7.2.exportfs
[1/4] nfsd/blocklayout: always ignore loca_time_modify
https://git.kernel.org/vfs/vfs/c/0d9ff5c4219f
[2/4] exportfs: split out the ops for layout-based block device access
https://git.kernel.org/vfs/vfs/c/d5758c31a81b
[3/4] exportfs: don't pass struct iattr to ->commit_blocks
https://git.kernel.org/vfs/vfs/c/61eb48f51585
[4/4] exportfs,nfsd: rework checking for layout-based block device access support
https://git.kernel.org/vfs/vfs/c/da9baa5470dc
prev parent reply other threads:[~2026-05-11 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 18:18 [PATCH v3 0/4] cleanup block-style layouts exports Chuck Lever
2026-04-23 18:18 ` [PATCH v3 1/4] nfsd/blocklayout: always ignore loca_time_modify Chuck Lever
2026-04-24 13:22 ` Christoph Hellwig
2026-04-24 14:05 ` Chuck Lever
2026-04-23 18:18 ` [PATCH v3 2/4] exportfs: split out the ops for layout-based block device access Chuck Lever
2026-04-23 18:18 ` [PATCH v3 3/4] exportfs: don't pass struct iattr to ->commit_blocks Chuck Lever
2026-04-23 18:18 ` [PATCH v3 4/4] exportfs,nfsd: rework checking for layout-based block device access support Chuck Lever
2026-05-11 9:15 ` 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=20260511-zombie-habilitation-08bc00f1a404@brauner \
--to=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@ownmail.net \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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 read-only IMAP folder(s) and NNTP newsgroup(s).