From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Daniel Díaz" <daniel.diaz@linaro.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
laoar.shao@gmail.com
Subject: Re: [PATCH 5.15 000/370] 5.15.111-rc2 review
Date: Thu, 11 May 2023 07:58:17 +0900 [thread overview]
Message-ID: <2023051154-activator-aside-bc8e@gregkh> (raw)
In-Reply-To: <4d3c5462-1788-426a-a44a-e839b1c4970d@roeck-us.net>
On Wed, May 10, 2023 at 12:53:48PM -0700, Guenter Roeck wrote:
> On Wed, May 10, 2023 at 11:00:42AM -0600, Daniel Díaz wrote:
> > Hello!
> >
> > On Wed, 10 May 2023 at 09:46, Daniel Díaz <daniel.diaz@linaro.org> wrote:
> > > Hello!
> > >
> > > On Wed, 10 May 2023 at 01:43, Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > > On Tue, May 09, 2023 at 09:12:33AM -0600, Daniel Díaz wrote:
> > > > > Hello!
> > > > >
> > > > > On 08/05/23 21:26, Greg Kroah-Hartman wrote:
> > > > > > This is the start of the stable review cycle for the 5.15.111 release.
> > > > > > There are 370 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 Thu, 11 May 2023 03:05:05 +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/v5.x/stable-review/patch-5.15.111-rc2.gz
> > > > > > or in the git tree and branch at:
> > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
> > > > > > and the diffstat can be found below.
> > > > > >
> > > > > > thanks,
> > > > > >
> > > > > > greg k-h
> > > > >
> > > > > New warnings are introduced for Arm, PowerPC, RISC-V:
> > > > >
> > > > > /builds/linux/kernel/sched/debug.c: In function 'print_cfs_group_stats':
> > > > > /builds/linux/kernel/sched/debug.c:465:41: warning: unused variable 'stats' [-Wunused-variable]
> > > > > struct sched_statistics *stats = __schedstats_from_se(se);
> > > > > ^~~~~
> > > >
> > > > Odd, and this isn't on other kernels too?
> > >
> > > Only on 5.15, not on the 6.x RC's. I'll share more info after my
> > > bisection is done.
> >
> > Bisection leads to:
> >
> > sched: Make struct sched_statistics independent of fair sched class
> >
> > Reverting makes the warning disappear.
> >
>
> Commit 769fdf83df57 ("sched: Fix DEBUG && !SCHEDSTATS warn") explains why
> this works upstream.
Thanks! Turns out someone put the wrong "Fixes:" tag in that commit
which is why I missed it. Now queued up.
greg k-h
next prev parent reply other threads:[~2023-05-10 22:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 3:26 [PATCH 5.15 000/370] 5.15.111-rc2 review Greg Kroah-Hartman
2023-05-09 5:59 ` Ron Economos
2023-05-09 8:39 ` Harshit Mogalapalli
2023-05-09 10:04 ` Bagas Sanjaya
2023-05-09 12:00 ` Chris Paterson
2023-05-09 13:35 ` Jon Hunter
2023-05-09 15:12 ` Daniel Díaz
2023-05-10 7:43 ` Greg Kroah-Hartman
2023-05-10 15:46 ` Daniel Díaz
2023-05-10 17:00 ` Daniel Díaz
2023-05-10 19:53 ` Guenter Roeck
2023-05-10 22:58 ` Greg Kroah-Hartman [this message]
2023-05-10 23:09 ` Linus Torvalds
2023-05-10 23:16 ` Greg Kroah-Hartman
2023-05-11 0:56 ` Stephen Rothwell
2023-05-10 19:09 ` Guenter Roeck
2023-05-09 16:49 ` Florian Fainelli
2023-05-09 17:03 ` Allen Pais
2023-05-09 19:54 ` Guenter Roeck
2023-05-10 8:51 ` Sudip Mukherjee (Codethink)
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=2023051154-activator-aside-bc8e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=daniel.diaz@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=laoar.shao@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.