linux-kernel - Re: [PATCH] mm/memory_hotplug: Rename all existing 'memhp' into 'mhp'

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] [day] [month] [year] [list]

Message-ID: <557ea028-6b6f-6f32-7602-70a62050a3e3@redhat.com>
Date:   Mon, 25 Jan 2021 09:54:49 +0100
From:   David Hildenbrand <david@...hat.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Anshuman Khandual <anshuman.khandual@....com>
Cc:     linux-mm@...ck.org, akpm@...ux-foundation.org,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/memory_hotplug: Rename all existing 'memhp' into 'mhp'

On 25.01.21 09:26, Greg Kroah-Hartman wrote:
> On Mon, Jan 25, 2021 at 11:24:53AM +0530, Anshuman Khandual wrote:
>> This renames all 'memhp' instances to 'mhp' except for memhp_default_state
>> for being a kernel command line option. This is just a clean up and should
>> not cause a functional change.
> 
> THat says _what_ you are doing, but I have no idea _why_ this is needed
> for anything...
> 

Let's add something like

"Let's make it consistent, especially preparing for more users of the
'mhp' terminology."


Reviewed-by: David Hildenbrand <david@...hat.com>

-- 
Thanks,

David / dhildenb