From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ron Economos <re@w6rz.net>
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, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 5.15 000/127] 5.15.177-rc2 review
Date: Thu, 23 Jan 2025 15:11:18 +0100 [thread overview]
Message-ID: <2025012347-storm-dance-adfc@gregkh> (raw)
In-Reply-To: <010553d5-4504-40d9-a358-8404f57ebe9a@w6rz.net>
On Wed, Jan 22, 2025 at 05:20:54AM -0800, Ron Economos wrote:
> On 1/22/25 00:03, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.177 release.
> > There are 127 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 Fri, 24 Jan 2025 07:38: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/v5.x/stable-review/patch-5.15.177-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
>
> The build fails with:
>
> drivers/usb/core/port.c: In function 'usb_port_shutdown':
> drivers/usb/core/port.c:299:26: error: 'struct usb_device' has no member
> named 'port_is_suspended'
> 299 | if (udev && !udev->port_is_suspended) {
> | ^~
> make[3]: *** [scripts/Makefile.build:289: drivers/usb/core/port.o] Error 1
> make[2]: *** [scripts/Makefile.build:552: drivers/usb/core] Error 2
> make[1]: *** [scripts/Makefile.build:552: drivers/usb] Error 2
>
> Same issue as with 6.1.125-rc1 last week. Needs the fixup patch in 6.1.126.
Ah, ick. It's hard for me to build with CONFIG_PM disabled here for
some reason. I'll go queue up my fix for this from 6.1, and then your
fix for my fix :)
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-23 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 8:03 [PATCH 5.15 000/127] 5.15.177-rc2 review Greg Kroah-Hartman
2025-01-22 13:20 ` Ron Economos
2025-01-22 19:45 ` Pavel Machek
2025-01-23 14:11 ` Greg Kroah-Hartman [this message]
2025-01-23 14:19 ` Ron Economos
2025-01-23 16:15 ` Greg Kroah-Hartman
2025-01-22 14:08 ` Naresh Kamboju
2025-01-22 14:15 ` Arnd Bergmann
2025-01-22 17:08 ` Mark Brown
2025-01-22 17:55 ` Florian Fainelli
2025-01-22 20:25 ` [PATCH 5.15] " Hardik Garg
2025-01-23 13:33 ` [PATCH 5.15 000/127] " Muhammad Usama Anjum
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=2025012347-storm-dance-adfc@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=re@w6rz.net \
--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