From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: 6.1.125 build fail was -- Re: [PATCH 6.1 00/92] 6.1.125-rc1 review
Date: Fri, 17 Jan 2025 22:16:04 +0100 [thread overview]
Message-ID: <Z4rIlESGC6mwi8HP@duo.ucw.cz> (raw)
In-Reply-To: <2025011725-underdog-heftiness-49df@gregkh>
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
Hi!
> > > Still building, but we already have failures on risc-v.
> > >
> > > drivers/usb/core/port.c: In function 'usb_port_shutdown':
> > > 2912
> > > drivers/usb/core/port.c:417:26: error: 'struct usb_device' has no member named 'port_is_suspended'
> > > 2913
> > > 417 | if (udev && !udev->port_is_suspended) {
> > > 2914
> > > | ^~
> > > 2915
> > > make[4]: *** [scripts/Makefile.build:250: drivers/usb/core/port.o] Error 1
> > > 2916
> > > make[4]: *** Waiting for unfinished jobs....
> > > 2917
> > > CC drivers/gpu/drm/radeon/radeon_test.o
> >
> > And there's similar failure on x86:
> >
> > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1626266073
>
> Thanks for testing and letting me know,
Ok, so it seems _this_ failure is fixed... but there's new one. Build
failure on risc-v.
LD .tmp_vmlinux.kallsyms1
2941
riscv64-linux-gnu-ld: drivers/usb/host/xhci-pci.o: in function `xhci_pci_resume':
2942
xhci-pci.c:(.text+0xd8c): undefined reference to `xhci_resume'
2943
riscv64-linux-gnu-ld: xhci-pci.c:(.text+0xe1a): undefined reference to `xhci_suspend'
2944
make[1]: *** [scripts/Makefile.vmlinux:34: vmlinux] Error 1
2945
make: *** [Makefile:1250: vmlinux] Error 2
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/8883180471
(I have also 2 runtime failures, I'm retrying those jobs.
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1630005263
). I partly reconsructed To:.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-01-17 21:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 10:36 Greg Kroah-Hartman
2025-01-15 12:50 ` Pavel Machek
2025-01-15 13:57 ` Pavel Machek
[not found] ` <2025011725-underdog-heftiness-49df@gregkh>
2025-01-17 21:16 ` Pavel Machek [this message]
2025-01-18 6:37 ` 6.1.125 build fail was -- " Ron Economos
2025-01-18 7:20 ` Greg Kroah-Hartman
2025-01-18 12:27 ` Ron Economos
2025-01-15 14:09 ` Ron Economos
2025-01-15 15:07 ` Greg Kroah-Hartman
2025-01-15 13:15 ` Mark Brown
2025-01-15 14:13 ` Jon Hunter
2025-01-15 22:14 ` Florian Fainelli
2025-01-15 22:32 ` Shuah Khan
2025-01-16 10:48 ` Naresh Kamboju
2025-01-16 13:59 ` Peter Schneider
2025-01-17 2:25 ` [PATCH 6.1] " Hardik Garg
2025-01-18 15:05 ` [PATCH 6.1 00/92] " Guenter Roeck
2025-01-18 15:34 ` Greg Kroah-Hartman
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=Z4rIlESGC6mwi8HP@duo.ucw.cz \
--to=pavel@denx.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®