From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Chuck Lever <cel@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: cleanup block-style layouts exports v2
Date: Tue, 14 Apr 2026 12:01:39 +0200 [thread overview]
Message-ID: <20260414-ausbrechen-gemixt-ff09f46bdad2@brauner> (raw)
In-Reply-To: <20260410111007.GA10292@lst.de>
On Fri, Apr 10, 2026 at 01:10:07PM +0200, Christoph Hellwig wrote:
> On Thu, Apr 09, 2026 at 03:26:09PM +0200, Christian Brauner wrote:
> > > Christian, are you OK if I take this series through the NFSD tree?
> >
> > Hm, I generally prefer infrastructure to go through the VFS tree.
> > You can get a stable branch ofc.
>
> Communicating this earlier would be helpful. If we switch to a new
> tree base we're going to miss this merge window.
The series was sent on April 1 so with about 2 weeks before the merge
window... If your series isn't ready by -rc5 what is it doing being
merged for the coming merge window is the other side of the question. So
afaict, there's no hurry.
next prev parent reply other threads:[~2026-04-14 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 14:40 cleanup block-style layouts exports v2 Christoph Hellwig
2026-04-01 14:40 ` [PATCH 1/4] nfsd/blocklayout: always ignore loca_time_modify Christoph Hellwig
2026-04-01 14:40 ` [PATCH 2/4] exportfs: split out the ops for layout-based block device access Christoph Hellwig
2026-04-01 14:40 ` [PATCH 3/4] exportfs: don't pass struct iattr to ->commit_blocks Christoph Hellwig
2026-04-01 14:40 ` [PATCH 4/4] exportfs,nfsd: rework checking for layout-based block device access support Christoph Hellwig
2026-04-13 22:28 ` Jeff Layton
2026-04-01 20:31 ` cleanup block-style layouts exports v2 Chuck Lever
2026-04-09 13:26 ` Christian Brauner
2026-04-10 11:10 ` Christoph Hellwig
2026-04-14 10:01 ` Christian Brauner [this message]
2026-04-15 5:29 ` Christoph Hellwig
2026-04-15 14:34 ` Chuck Lever
2026-04-17 14:52 ` Chuck Lever
2026-04-21 12:04 ` Christian Brauner
2026-04-23 18:57 ` Jeff Layton
2026-04-27 15:03 ` Christian Brauner
2026-04-16 9:27 ` Christian Brauner
2026-04-02 21:09 ` Chuck Lever
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=20260414-ausbrechen-gemixt-ff09f46bdad2@brauner \
--to=brauner@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=amir73il@gmail.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.