[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220703135708.kn535pdrqv24f7kn@ava.usersys.com>
Date: Sun, 3 Jul 2022 14:57:08 +0100
From: Aaron Tomlin <atomlin@...hat.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Luis Chamberlain <mcgrof@...nel.org>, christophe.leroy@...roup.eu,
cl@...ux.com, mbenes@...e.cz, akpm@...ux-foundation.org,
jeyu@...nel.org, linux-kernel@...r.kernel.org,
linux-modules@...r.kernel.org, void@...ifault.com,
atomlin@...mlin.com, allen.lkml@...il.com, joe@...ches.com,
msuchanek@...e.de, oleksandr@...alenko.name,
jason.wessel@...driver.com, pmladek@...e.com,
daniel.thompson@...aro.org, hch@...radead.org,
Chuck Lever III <chuck.lever@...cle.com>
Subject: Re: [PATCH v11 09/14] module: Move kallsyms support into a separate
file
On Sun 2022-07-03 09:23 -0400, Steven Rostedt wrote:
> BTW, *NEVER* modify code that you are moving. Really, *NEVER* do that!
>
> It makes debugging much more difficult, like in this very case.
>
> *ALWAYS* have the moving of code be a separate patch. Keep as most
> identical as humanly possible. Even keep white space errors the same!
> You can add a clean up patch before or after the move. But never do it
> as one patch!
Hi Steve,
I completely agree and noted.
> You even stated "no functional change" which was a lie. Converting
> strlcpy() to strscpy() *is* a functional change!
Understood.
Kind regards,
--
Aaron Tomlin
Powered by blists - more mailing lists