[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e21c6dbb-7083-4425-bace-6194bfbf35b7@oracle.com>
Date: Wed, 31 Jan 2024 17:16:09 +0000
From: John Garry <john.g.garry@...cle.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: mcgrof@...nel.org, russ.weight@...ux.dev, rafael@...nel.org,
rostedt@...dmis.org, mhiramat@...nel.org,
mathieu.desnoyers@...icios.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
keescook@...omium.org, masahiroy@...nel.org, nathan@...nel.org,
nicolas@...sle.eu, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-kbuild@...r.kernel.org
Subject: Re: [PATCH RFC 0/4] Introduce uts_release
On 31/01/2024 16:22, Greg KH wrote:
>> before:
>> real 0m53.591s
>> user 1m1.842s
>> sys 0m9.161s
>>
>> after:
>> real 0m37.481s
>> user 0m46.461s
>> sys 0m7.199s
>>
>> Sending as an RFC as I need to test more of the conversions and I would
>> like to also convert more UTS_RELEASE users to prove this is proper
>> approach.
> I like it, I also think that v4l2 includes this as well as all of those
> drivers seem to rebuild when this changes, does that not happen for you
> too?
I didn't see that. Were you were building for arm64? I can see some v4l2
configs enabled there for the vanilla defconfig (but none for x86-64).
>
> Anyway, if the firmware changes work, I'm all for this, thanks for
> taking it on!
cheers. BTW, I just noticed that utsrelase.h might not be updated for my
allmodconfig build when I change the head commit - I'll investigate why ...
John
Powered by blists - more mailing lists