From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Helge Deller <deller@gmx.de>
Cc: Guenter Roeck <linux@roeck-us.net>,
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,
conor@kernel.org, allen.lkml@gmail.com
Subject: Re: [PATCH 4.14 00/53] 4.14.331-rc2 review
Date: Mon, 27 Nov 2023 12:47:03 +0000 [thread overview]
Message-ID: <2023112751-predict-ovary-5afa@gregkh> (raw)
In-Reply-To: <ZWOs6uwZoCoxYSSs@p100>
On Sun, Nov 26, 2023 at 09:39:06PM +0100, Helge Deller wrote:
> * Guenter Roeck <linux@roeck-us.net>:
> > On 11/25/23 08:32, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.14.331 release.
> > > There are 53 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 Mon, 27 Nov 2023 16:30:48 +0000.
> > > Anything received after that time might be too late.
> > >
> >
> > Building parisc64:generic-64bit_defconfig ... failed
> > --------------
> > Error log:
> > hppa64-linux-ld: arch/parisc/kernel/head.o: in function `$iodc_panic':
> > (.head.text+0x64): undefined reference to `init_stack'
> > hppa64-linux-ld: (.head.text+0x68): undefined reference to `init_stack'
> > make[1]: *** [Makefile:1049: vmlinux] Error 1
> > make: *** [Makefile:153: sub-make] Error 2
>
> Indeed.
> Thanks for testing, Guenter!
>
> Greg, could you please replace the patch in queue/4.14 with
> the one below? It simply uses another stack start, which is ok since the
> machine will stop anyway.
>
> No changes needed for your other stable-queues. I tested 4.19 and
> it's ok as-is.
>
Now replaced, thanks.
greg k-h
next prev parent reply other threads:[~2023-11-27 13:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 16:32 [PATCH 4.14 00/53] 4.14.331-rc2 review Greg Kroah-Hartman
2023-11-25 20:10 ` Pavel Machek
2023-11-26 18:33 ` Guenter Roeck
2023-11-26 20:39 ` Helge Deller
2023-11-27 12:47 ` Greg Kroah-Hartman [this message]
2023-11-27 5:47 ` Harshit Mogalapalli
2023-11-27 14:33 ` Naresh Kamboju
2023-11-27 20:51 ` Pavel Machek
2023-11-28 13:10 ` Ilpo Järvinen
2023-11-28 20:39 ` Pavel Machek
2023-11-28 20:43 ` Greg Kroah-Hartman
2023-11-28 20:48 ` Pavel Machek
2023-11-28 21:10 ` Greg Kroah-Hartman
2023-11-29 9:00 ` Pavel Machek
2023-11-29 17:45 ` Sasha Levin
2023-11-29 11:20 ` Ilpo Järvinen
2023-11-27 23:25 ` Jon Hunter
2023-11-28 2:49 ` Guenter Roeck
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=2023112751-predict-ovary-5afa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=conor@kernel.org \
--cc=deller@gmx.de \
--cc=f.fainelli@gmail.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