From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, david@redhat.com,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/memory_hotplug: Rename all existing 'memhp' into 'mhp'
Date: Mon, 25 Jan 2021 14:21:02 +0530 [thread overview]
Message-ID: <3dc093e6-e037-c67c-f2f9-c534fdabdd99@arm.com> (raw)
In-Reply-To: <YA6AqupAWINtNckx@kroah.com>
On 1/25/21 1:56 PM, 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...
There is a series [1] which adds some new hotplug functions starting
with mhp_ (after deciding in its favor rather than memhp_). We should
have a common naming scheme either memhp_ based or mhp_ based but not
mixed. As it was proposed [2] to go with mhp_ based names instead, all
the existing memhp_ needed renaming. Hence the this patch.
[1] https://lore.kernel.org/linux-mm/1611543532-18698-1-git-send-email-anshuman.khandual@arm.com/
[2] https://lore.kernel.org/linux-mm/c37de2d0-28a1-4f7d-f944-cfd7d81c334d@redhat.com/
- Anshuman
next prev parent reply other threads:[~2021-01-25 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 5:54 Anshuman Khandual
2021-01-25 8:26 ` Greg Kroah-Hartman
2021-01-25 8:51 ` Anshuman Khandual [this message]
2021-01-25 9:25 ` Greg Kroah-Hartman
2021-01-25 8:54 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3dc093e6-e037-c67c-f2f9-c534fdabdd99@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox