From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Florian Fainelli <f.fainelli@gmail.com>
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@denx.de, jonathanh@nvidia.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 000/772] 6.1.120-rc1 review
Date: Fri, 13 Dec 2024 13:33:38 +0100 [thread overview]
Message-ID: <2024121342-fastball-batting-c80b@gregkh> (raw)
In-Reply-To: <c356563b-4137-403f-9f0f-29e9b38512ce@gmail.com>
On Thu, Dec 12, 2024 at 01:38:31PM -0800, Florian Fainelli wrote:
> On 12/12/24 06:49, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.120 release.
> > There are 772 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 Sat, 14 Dec 2024 14:41:35 +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.1.120-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.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on
> BMIPS_GENERIC:
>
> Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
>
> There is a new warning though:
>
> scripts/mod/modpost.c:969:44: warning: excess elements in array initializer
> 969 | .good_tosec = {ALL_TEXT_SECTIONS , NULL},
> | ^~~~
> scripts/mod/modpost.c:969:44: note: (near initialization for
> ‘sectioncheck[10].good_tosec’)
> HOSTLD scripts/mod/modpost
I thought I saw that but kind of ignored it, but in looking at it
further, it's not good at all. Let me go fix this up, for some reason
we have "too many" entries in this list and so we could flow over the
end of the buffer here...
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-13 12:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 14:49 [PATCH 6.1 000/772] 6.1.120-rc1 review Greg Kroah-Hartman
2024-12-12 14:53 ` [PATCH 6.1 281/772] m68k: coldfire/device.c: only build FEC when HW macros are defined Greg Kroah-Hartman
2024-12-12 15:01 ` [PATCH 6.1 761/772] drm/ttm: Make sure the mapped tt pages are decrypted when needed Greg Kroah-Hartman
2024-12-12 15:01 ` [PATCH 6.1 762/772] drm/ttm: Print the memory decryption status just once Greg Kroah-Hartman
2024-12-12 16:25 ` [PATCH 6.1 000/772] 6.1.120-rc1 review Pavel Machek
2024-12-12 20:59 ` Naresh Kamboju
2024-12-13 12:24 ` Greg Kroah-Hartman
2024-12-12 21:38 ` Florian Fainelli
2024-12-13 12:33 ` Greg Kroah-Hartman [this message]
2024-12-13 2:30 ` Peter Schneider
2024-12-13 2:44 ` Ron Economos
2024-12-13 14:17 ` Greg Kroah-Hartman
2024-12-13 10:03 ` Jon Hunter
2024-12-13 13:13 ` Mark Brown
2024-12-13 17:06 ` Shuah Khan
2024-12-13 18:35 ` SeongJae Park
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=2024121342-fastball-batting-c80b@gregkh \
--to=gregkh@linuxfoundation.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@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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