[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ec2304d7-62e8-4d4f-a838-e4decd78d147@gmail.com>
Date: Sun, 16 Jun 2024 13:55:58 +0100
From: Florian Fainelli <f.fainelli@...il.com>
To: Vegard Nossum <vegard.nossum@...cle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
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,
Kamalesh Babulal <kamalesh.babulal@...cle.com>, pavel@...x.de,
jonathanh@...dia.com, sudipm.mukherjee@...il.com, srw@...dewatkins.net,
rwarsow@....de, conor@...nel.org, allen.lkml@...il.com, broonie@...nel.org,
acme@...hat.com, namhyung@...nel.org, gpavithrasha@...il.com,
irogers@...gle.com, Darren Kenny <darren.kenny@...cle.com>
Subject: Re: [PATCH 5.15 000/402] 5.15.161-rc1 review
On 6/15/2024 7:09 PM, Vegard Nossum wrote:
>
> On 15/06/2024 13:05, Greg Kroah-Hartman wrote:
>> On Fri, Jun 14, 2024 at 02:10:26PM +0530, Harshit Mogalapalli wrote:
>>> I think building perf while adding perf patches would help us prevent
>>> from
>>> running into this issue. cd tools/perf/ ; make -j$(nproc) all
>>
>> Maybe, but I can't seem to build perf at all for quite a while, so I
>> doubt that anyone really cares here, right?
>
> We're building perf and it worked before these patches. It's part of our
> kernel build and we do ship the result to customers. So we care :-)
Likewise here, we care about making sure that perf builds and works for
any given stable release stream.
--
Florian
Powered by blists - more mailing lists