[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8271eb39-c44d-37ed-7501-e9d05d7fee17@huawei.com>
Date: Tue, 2 Mar 2021 14:42:15 +0800
From: Hanjun Guo <guohanjun@...wei.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
<linux-kernel@...r.kernel.org>
CC: <torvalds@...ux-foundation.org>, <akpm@...ux-foundation.org>,
<linux@...ck-us.net>, <shuah@...nel.org>, <patches@...nelci.org>,
<lkft-triage@...ts.linaro.org>, <pavel@...x.de>,
<jonathanh@...dia.com>, <f.fainelli@...il.com>,
<stable@...r.kernel.org>, <zou_wei@...wei.com>,
Yanjin <yanjin.yan@...wei.com>
Subject: Re: [PATCH 5.4 000/340] 5.4.102-rc1 review
Hi Greg,
On 2021/3/2 0:09, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.102 release.
> There are 340 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, 03 Mar 2021 16:09:49 +0000.
> Anything received after that time might be too late.
Our test CI monitored the 5.4.102-rc2, and compile failure:
kernel/rcu/tree.c:617:2: error: implicit declaration of function
‘IRQ_WORK_INIT’; did you mean ‘IRQ_WORK_BUSY’?
[-Werror=implicit-function-declaration]
IRQ_WORK_INIT(late_wakeup_func);
^~~~~~~~~~~~~
IRQ_WORK_BUSY
kernel/rcu/tree.c:617:2: error: invalid initializer
Should be commit e1e41aa31ed1 (rcu/nocb: Trigger self-IPI on late
deferred wake up before user resume) fails the build.
By the way, do you expect us test the 5.4.102-rc1 or the
5.4.102-rc2 in your tree?
Thanks
Hanjun
Powered by blists - more mailing lists