linux-kernel - Re: [PATCH 1/2] init/main.c: fix strings split across lines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210112161124.2789c67e@gandalf.local.home>
Date:   Tue, 12 Jan 2021 16:11:24 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Liu Peibao <liupeibao@....com>
Cc:     mhiramat@...nel.org, akpm@...ux-foundation.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] init/main.c: fix strings split across lines

On Tue, 12 Jan 2021 22:26:21 +0800
Liu Peibao <liupeibao@....com> wrote:

> Thanks for your replay! I get it.
> But I still feel a little confused that we use different standard to 
> measure the existing code and the new code. I also checked some commits, 
> there are similar patches too.

For the reason of different standards for existing code to new code. Think
of it as a "grandfather clause". Where rules change for new instantiations,
but if you already have something, you can still use the old rules. Hmm,
it's kind of like how RCU works!

As for some commits getting it. They sometimes get pulled in by various
maintainers, and also may happen if you are changing the code around
something. With the "one commit does one thing", you can have a "clean up
code" patch followed by a "change the code" patch. matters what the context
is.

-- Steve