From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
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,
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 4.19 000/138] 4.19.325-rc1 review
Date: Thu, 5 Dec 2024 10:36:38 +0100 [thread overview]
Message-ID: <2024120503-eloquent-exemption-b3e7@gregkh> (raw)
In-Reply-To: <Z1A+Ku5D0OFOSUm4@duo.ucw.cz>
On Wed, Dec 04, 2024 at 12:34:02PM +0100, Pavel Machek wrote:
> Hi!
>
> > > > This is the start of the stable review cycle for the 4.19.325 release.
> > > > There are 138 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.
> > >
> > > Build fails:
> > >
> > > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/8532423815
> > >
> > > CC drivers/pinctrl/uniphier/pinctrl-uniphier-pro4.o
> > > 3895
> > > CC drivers/pci/of.o
> > > 3896
> > > drivers/rtc/rtc-st-lpc.c: In function 'st_rtc_probe':
> > > 3897
> > > drivers/rtc/rtc-st-lpc.c:233:11: error: 'IRQF_NO_AUTOEN' undeclared (first use in this function); did you mean 'IRQ_NOAUTOEN'?
> > > 3898
> > > IRQF_NO_AUTOEN, pdev->name, rtc);
> > > 3899
> > > ^~~~~~~~~~~~~~
> > > 3900
> > > IRQ_NOAUTOEN
> > > 3901
> > > drivers/rtc/rtc-st-lpc.c:233:11: note: each undeclared identifier is reported only once for each function it appears in
> > > 3902
> > > CC drivers/pci/quirks.o
> > > 3903
> > > make[2]: *** [scripts/Makefile.build:303: drivers/rtc/rtc-st-lpc.o] Error 1
> > > 3904
> > > make[1]: *** [scripts/Makefile.build:544: drivers/rtc] Error 2
> > > 3905
> > > make[1]: *** Waiting for unfinished jobs....
> > > 3906
> > > CC drivers/pinctrl/uniphier/pinctrl-uniphier-sld8.o
> > > 3907
> > > CC drivers/soc/renesas/r8a7743-sysc.o
> >
> > What arch is this? And can you not wrap error logs like this please?
>
> Not easily. But you can easily get nicely formatted logs +
> architecture details by clicking the hyperlink above.
Sometimes we don't have web access, only email access. Putting all of
the relevant information in the report is best please, if you wish for
anyone to pay attention to it (i.e. don't make me do extra work for your
test systems...)
I found the offending commit, I think. Funnily it used IRQ_NOAUTOEN
which is also in other files in 4.19.y yet never defined, so our test
coverage isn't all that good these days. All the more reason this
kernel needs to be marked end-of-life and never used again.
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-05 9:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 14:30 Greg Kroah-Hartman
2024-12-03 14:31 ` [PATCH 4.19 080/138] m68k: coldfire/device.c: only build FEC when HW macros are defined Greg Kroah-Hartman
2024-12-03 18:13 ` [PATCH 4.19 000/138] 4.19.325-rc1 review Pavel Machek
2024-12-04 9:48 ` Greg Kroah-Hartman
2024-12-04 11:34 ` Pavel Machek
2024-12-05 9:36 ` Greg Kroah-Hartman [this message]
2024-12-04 13:54 ` Naresh Kamboju
2024-12-04 15:32 ` Naresh Kamboju
2024-12-05 9:33 ` Greg Kroah-Hartman
2024-12-04 14:28 ` Harshit Mogalapalli
2024-12-04 16:56 ` Shuah Khan
2024-12-05 14:38 ` Jon Hunter
2024-12-05 14:40 ` Jon Hunter
2024-12-06 6:07 ` Greg Kroah-Hartman
2024-12-06 10:39 ` Jon Hunter
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=2024120503-eloquent-exemption-b3e7@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
all inboxes | Powered by JetHome®