From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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,
stable@vger.kernel.org
Subject: Re: [PATCH 5.10 000/156] 5.10.26-rc2 review
Date: Mon, 22 Mar 2021 14:05:58 -0700 [thread overview]
Message-ID: <20210322210558.GA52477@roeck-us.net> (raw)
In-Reply-To: <20210322151845.637893645@linuxfoundation.org>
On Mon, Mar 22, 2021 at 04:19:10PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.26 release.
> There are 156 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 Wed, 24 Mar 2021 15:18:19 +0000.
> Anything received after that time might be too late.
>
Building arm:realview-pb-a8:realview_defconfig:realview_pb:mem512:arm-realview-pba8:initrd ... failed
------------
Error log:
kernel/rcu/tree.c:683:2: error: implicit declaration of function 'IRQ_WORK_INIT' [-Werror=implicit-function-declaration]
683 | IRQ_WORK_INIT(late_wakeup_func);
| ^~~~~~~~~~~~~
kernel/rcu/tree.c:683:2: error: invalid initializer
$ git reset --hard local-stable/linux-5.10.y.queue
HEAD is now at deabac90f919 Linux 5.10.26-rc2
$ git grep IRQ_WORK_INIT
kernel/rcu/tree.c: IRQ_WORK_INIT(late_wakeup_func);
$ git describe
v5.10.25-157-gdeabac90f919
Guenter
next prev parent reply other threads:[~2021-03-22 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 15:19 [PATCH 5.10 000/156] 5.10.26-rc2 review Greg Kroah-Hartman
2021-03-22 18:50 ` Florian Fainelli
2021-03-22 20:13 ` Pavel Machek
2021-03-22 21:05 ` Guenter Roeck [this message]
2021-03-22 21:52 ` Guenter Roeck
2021-03-23 7:19 ` Greg Kroah-Hartman
2021-03-23 0:47 ` Samuel Zou
2021-03-23 0:57 ` Samuel Zou
2021-03-23 8:49 ` Naresh Kamboju
2021-03-24 8:52 ` Naresh Kamboju
2021-03-23 17:21 ` Andrei Rabusov
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=20210322210558.GA52477@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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.