[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250818201403.33f469f169957d46ef061d52@linux-foundation.org>
Date: Mon, 18 Aug 2025 20:14:03 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Pankaj Raghav <p.raghav@...sung.com>
Cc: André Almeida <andrealmeid@...lia.com>, Christoph Hellwig
<hch@...radead.org>, Christian Brauner <brauner@...nel.org>, Stephen
Rothwell <sfr@...b.auug.org.au>, "Darrick J . Wong" <djwong@...nel.org>,
"Pankaj Raghav (Samsung)" <kernel@...kajraghav.com>,
<linux-kernel@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
<mcgrof@...nel.org>, <gost.dev@...sung.com>, <linux-xfs@...r.kernel.org>
Subject: Re: [PATCH] iomap: use largest_zero_folio() in iomap_dio_zero()
On Mon, 18 Aug 2025 16:35:04 +0200 Pankaj Raghav <p.raghav@...sung.com> wrote:
> >>> Applied to the vfs-6.18.iomap branch of the vfs/vfs.git tree.
> >>> Patches in the vfs-6.18.iomap branch should appear in linux-next soon.
> >>
> >> Hmm, AFAIK largest_zero_folio just showed up in mm.git a few days ago.
> >> Wouldn't it be better to queue up this change there?
> >>
> >>
> >
> > Indeed, compiling vfs/vfs.all as of today fails with:
> >
> > fs/iomap/direct-io.c:281:36: error: implicit declaration of function
> > ‘largest_zero_folio’; did you mean ‘is_zero_folio’? [-Wimplicit-
> > function-declaration]
> >
> > Reverting "iomap: use largest_zero_folio() in iomap_dio_zero()" fixes
> > the compilation.
> >
>
> I also got some reports from Stephen in linux-next. As Christoph
> suggested, maybe we drop the patches from Christian's tree and queue it
> up via Andrew's tree
Thanks, I added it to mm.git.
Powered by blists - more mailing lists