[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251125111402.GB22313@lst.de>
Date: Tue, 25 Nov 2025 12:14:02 +0100
From: Christoph Hellwig <hch@....de>
To: Christian Brauner <brauner@...nel.org>
Cc: Christoph Hellwig <hch@....de>, Al Viro <viro@...iv.linux.org.uk>,
David Sterba <dsterba@...e.com>, Jan Kara <jack@...e.cz>,
Mike Marshall <hubcap@...ibond.com>,
Martin Brandenburg <martin@...ibond.com>,
Carlos Maiolino <cem@...nel.org>, Stefan Roesch <shr@...com>,
Jeff Layton <jlayton@...nel.org>, linux-kernel@...r.kernel.org,
linux-btrfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
gfs2@...ts.linux.dev, io-uring@...r.kernel.org,
devel@...ts.orangefs.org, linux-unionfs@...r.kernel.org,
linux-mtd@...ts.infradead.org, linux-xfs@...r.kernel.org,
linux-nfs@...r.kernel.org
Subject: Re: re-enable IOCB_NOWAIT writes to files v2
On Tue, Nov 25, 2025 at 10:18:32AM +0100, Christian Brauner wrote:
> It's a bit too close to the merge window for my taste and we have about
> 17 pull request topics for this cycle already.
>
> So I'll take this for vfs-6.20.iomap. As usual I'll create that branch
> now so that the patches don't get lost and will rebase once v6.19-rc1 is
> out.
I can understand that. Although it would be nice to get the nfsd
and btrfs fixes in, i.e. patch 1-4 (and 5/6 are trivial and would be
neat as well). I'll need to resend the others anyway based on the
(minor) review feedback, which I'll do right after -rc1.
Powered by blists - more mailing lists