On Tue, Jan 07, 2025 at 03:01:56PM +0200, Mike Rapoport wrote: > On Tue, Jan 07, 2025 at 03:54:43PM +0530, Naresh Kamboju wrote: > > On Mon, 6 Jan 2025 at 20:53, Greg Kroah-Hartman > > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > This is the start of the stable review cycle for the 6.6.70 release. > > > There are 222 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. > > > > > > Responses should be made by Wed, 08 Jan 2025 15:11:04 +0000. > > > Anything received after that time might be too late. > > > > > > The whole patch series can be found in one patch at: > > > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.6.70-rc1.gz > > > or in the git tree and branch at: > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > > > As others have reported, boot warnings on x86 have been noticed > > > > memblock: make memblock_set_node() also warn about use of MAX_NUMNODES > > [ Upstream commit e0eec24e2e199873f43df99ec39773ad3af2bff7 ] > > There's 8043832e2a12 ("memblock: use numa_valid_node() helper to check for > invalid node ID") that fixes it Thanks. I'll drop the offending commit for now and then add this, and the fix, back in for the next round of -rc releases to get testing on it. greg k-h
