From: Andrew Morton <akpm@linux-foundation.org>
To: Pankaj Raghav <p.raghav@samsung.com>
Cc: "André Almeida" <andrealmeid@igalia.com>,
"Christoph Hellwig" <hch@infradead.org>,
"Christian Brauner" <brauner@kernel.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Darrick J . Wong" <djwong@kernel.org>,
"Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
mcgrof@kernel.org, gost.dev@samsung.com,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] iomap: use largest_zero_folio() in iomap_dio_zero()
Date: Mon, 18 Aug 2025 20:14:03 -0700 [thread overview]
Message-ID: <20250818201403.33f469f169957d46ef061d52@linux-foundation.org> (raw)
In-Reply-To: <43bca78e-fa89-4b0e-94f1-de7385818950@samsung.com>
On Mon, 18 Aug 2025 16:35:04 +0200 Pankaj Raghav <p.raghav@samsung.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.
next prev parent reply other threads:[~2025-08-19 3:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 14:21 Pankaj Raghav (Samsung)
2025-08-14 18:27 ` Darrick J. Wong
2025-08-14 21:18 ` Pankaj Raghav (Samsung)
2025-08-15 14:02 ` Christian Brauner
2025-08-18 4:41 ` Christoph Hellwig
2025-08-18 14:12 ` André Almeida
2025-08-18 14:35 ` Pankaj Raghav
2025-08-19 3:14 ` Andrew Morton [this message]
2025-08-19 9:29 ` Christian Brauner
2025-10-07 9:56 ` Pankaj Raghav
2025-10-07 11:19 ` 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=20250818201403.33f469f169957d46ef061d52@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hch@infradead.org \
--cc=kernel@pankajraghav.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®