[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zro_AeCacGaLL3jq@bombadil.infradead.org>
Date: Mon, 12 Aug 2024 09:57:37 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Song Liu <song@...nel.org>, Nick Desaulniers <ndesaulniers@...gle.com>,
Nathan Chancellor <nathan@...nel.org>, "KE.LI" <like1@...o.com>,
Padmanabha Srinivasaiah <treasure4paddy@...il.com>,
Sami Tolvanen <samitolvanen@...gle.com>,
Fangrui Song <maskray@...gle.com>
Cc: live-patching@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, jpoimboe@...nel.org,
jikos@...nel.org, mbenes@...e.cz, pmladek@...e.com,
joe.lawrence@...hat.com, morbo@...gle.com, justinstitt@...gle.com,
thunder.leizhen@...wei.com, kees@...nel.org, kernel-team@...a.com,
mmaurer@...gle.com, mhiramat@...nel.org, rostedt@...dmis.org
Subject: Re: [PATCH v3 0/2] Fix kallsyms with CONFIG_LTO_CLANG
On Mon, Aug 12, 2024 at 09:21:02AM -0700, Song Liu wrote:
> Hi folks,
>
> Do we have more concerns and/or suggestions with this set? If not,
> what would be the next step for it?
I'm all for simplifying things, and this does just that, however,
I'm not the one you need to convince, the folks who added the original
hacks should provide their Reviewed-by / Tested-by not just for CONFIG_LTO_CLANG
but also given this provides an alternative fix, don't we want to invert
the order so we don't regress CONFIG_LTO_CLANG ? And shouldn't the patches
also have their respective Fixes tag?
Provided the commit logs are extended with Fixes and order is maintained
to be able to bisect correctly:
Reviewed-by: Luis Chamberlain <mcgrof@...nel.org>
Luis
Powered by blists - more mailing lists