linux-kernel - Re: [PATCH printk v4 04/39] printk: register_console: use "registered" for variable names

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: <Y3NxbSGNxBQZ8oW1@alley>
Date:   Tue, 15 Nov 2022 12:01:01 +0100
From:   Petr Mladek <pmladek@...e.com>
To:     John Ogness <john.ogness@...utronix.de>
Cc:     Sergey Senozhatsky <senozhatsky@...omium.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH printk v4 04/39] printk: register_console: use
 "registered" for variable names

On Mon 2022-11-14 17:34:57, John Ogness wrote:
> The @bootcon_enabled and @realcon_enabled local variables actually
> represent if such console types are registered. In general there
> has been a confusion about enabled vs. registered. Incorrectly
> naming such variables promotes such confusion.
> 
> Rename the variables to _registered.
> 
> Signed-off-by: John Ogness <john.ogness@...utronix.de>

I like this:

Reviewed-by: Petr Mladek <pmladek@...e.com>

Best Regards,
Petr