On 1/26/21 4:30 AM, akpm@xxxxxxxxxxxxxxxxxxxx wrote: > > The patch titled > Subject: mm/memory_hotplug: rename all existing 'memhp' into 'mhp' > has been added to the -mm tree. Its filename is > mm-memory_hotplug-rename-all-existing-memhp-into-mhp.patch > > This patch should soon appear at > https://ozlabs.org/~akpm/mmots/broken-out/mm-memory_hotplug-rename-all-existing-memhp-into-mhp.patch > and later at > https://ozlabs.org/~akpm/mmotm/broken-out/mm-memory_hotplug-rename-all-existing-memhp-into-mhp.patch > > Before you just go and hit "reply", please: > a) Consider who else should be cc'ed > b) Prefer to cc a suitable mailing list as well > c) Ideally: find the original patch on the mailing list and do a > reply-to-all to that, adding suitable additional cc's > > *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** > > The -mm tree is included into linux-next and is updated > there every 3-4 working days > > ------------------------------------------------------ > From: Anshuman Khandual <anshuman.khandual@xxxxxxx> > Subject: mm/memory_hotplug: rename all existing 'memhp' into 'mhp' > > 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. Let's make it consistent rater than > mixing the two prefixes. In preparation for more users of the 'mhp' > terminology. Thanks Andrew for updating the commit message here, which I assume is now complete. But otherwise please do let me know, will be happy to respin the patch with additional context as mentioned earlier in the thread. - Anshuman
