[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c7353c6f-c7d2-efa7-cb52-757325ec927f@huawei.com>
Date: Tue, 2 Mar 2021 20:56:04 +0800
From: Hanjun Guo <guohanjun@...wei.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: <linux-kernel@...r.kernel.org>, <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
On 2021/3/2 20:31, Greg Kroah-Hartman wrote:
> On Tue, Mar 02, 2021 at 02:42:15PM +0800, Hanjun Guo wrote:
>> 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.
> Ah, thank you, I'll go fix that up. Looks like 5.10.y also fails with
> that issue...
It is, same compile error for 5.10. I just confirmed both arm64 and
x86 have the same compile error.
Thanks
Hanjun
Powered by blists - more mailing lists