From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, achill@achill.org, sr@sladewatkins.com
Subject: Re: [PATCH 6.18 000/641] 6.18.14-rc1 review
Date: Wed, 25 Feb 2026 06:52:15 -0800 [thread overview]
Message-ID: <2026022501-linked-baking-3cee@gregkh> (raw)
In-Reply-To: <457362d4-c400-47a2-834b-327ded7d6192@sirena.org.uk>
On Wed, Feb 25, 2026 at 11:43:11AM +0000, Mark Brown wrote:
> On Tue, Feb 24, 2026 at 05:15:26PM -0800, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.18.14 release.
> > There are 641 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
>
> > Kevin Brodsky <kevin.brodsky@arm.com>
> > selftests/mm: fix faulting-in code in pagemap_ioctl test
>
> This breaks the build of the mm selftests:
>
> CC pagemap_ioctl
> pagemap_ioctl.c: In function ‘sanity_tests’:
> pagemap_ioctl.c:1169:9: error: implicit declaration of function ‘force_read_pages’ [-Wimplicit-function-declaration]
> 1169 | force_read_pages(fmem, nr_pages, page_size);
> | ^~~~~~~~~~~~~~~~
>
> IIRC there was a patch adding that function.
thanks, I've dropped this from all queues now, and will push out a -rc2
in a bit.
greg k-h
next prev parent reply other threads:[~2026-02-25 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 1:15 [PATCH 6.18 000/641] 6.18.14-rc1 review Greg Kroah-Hartman
2026-02-25 7:05 ` Shung-Hsi Yu
2026-02-25 9:25 ` Ron Economos
2026-02-25 11:42 ` Jon Hunter
2026-02-25 11:43 ` Mark Brown
2026-02-25 14:52 ` Greg Kroah-Hartman [this message]
2026-02-25 14:35 ` Jeffrin Thalakkottoor
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=2026022501-linked-baking-3cee@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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