From: Oscar Salvador <osalvador@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-mm@kvack.org, akpm@linux-foundation.org, hca@linux.ibm.com,
catalin.marinas@arm.com, Vasily Gorbik <gor@linux.ibm.com>,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 0/3] mm/memory_hotplug: Pre-validate the address range with platform
Date: Tue, 19 Jan 2021 14:40:21 +0100 [thread overview]
Message-ID: <20210119134016.GA23408@linux> (raw)
In-Reply-To: <d57036a1-de12-2d32-be65-daaa3dc5b772@redhat.com>
On Tue, Jan 19, 2021 at 02:33:03PM +0100, David Hildenbrand wrote:
> Minor thing, we should make up our mind if we want to call stuff
> internally "memhp_" or "mhp". I prefer the latter, because it is shorter.
I would rather use the latter as well. I used that in [1].
MEMHP_MERGE_RESOURCE should be renamed if we agree on that.
[1] https://patchwork.kernel.org/project/linux-mm/cover/20201217130758.11565-1-osalvador@suse.de/
--
Oscar Salvador
SUSE L3
WARNING: multiple messages have this Message-ID (diff)
From: Oscar Salvador <osalvador@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-s390@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
catalin.marinas@arm.com, hca@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, Will Deacon <will@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 0/3] mm/memory_hotplug: Pre-validate the address range with platform
Date: Tue, 19 Jan 2021 14:40:21 +0100 [thread overview]
Message-ID: <20210119134016.GA23408@linux> (raw)
In-Reply-To: <d57036a1-de12-2d32-be65-daaa3dc5b772@redhat.com>
On Tue, Jan 19, 2021 at 02:33:03PM +0100, David Hildenbrand wrote:
> Minor thing, we should make up our mind if we want to call stuff
> internally "memhp_" or "mhp". I prefer the latter, because it is shorter.
I would rather use the latter as well. I used that in [1].
MEMHP_MERGE_RESOURCE should be renamed if we agree on that.
[1] https://patchwork.kernel.org/project/linux-mm/cover/20201217130758.11565-1-osalvador@suse.de/
--
Oscar Salvador
SUSE L3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-19 13:40 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 13:12 [PATCH V3 0/3] mm/memory_hotplug: Pre-validate the address range with platform Anshuman Khandual
2021-01-18 13:12 ` Anshuman Khandual
2021-01-18 13:12 ` [PATCH V3 1/3] mm/memory_hotplug: Prevalidate the address range being added " Anshuman Khandual
2021-01-18 13:12 ` Anshuman Khandual
2021-01-19 12:21 ` David Hildenbrand
2021-01-19 12:21 ` David Hildenbrand
2021-01-20 8:33 ` Anshuman Khandual
2021-01-20 8:33 ` Anshuman Khandual
2021-01-20 10:41 ` David Hildenbrand
2021-01-20 10:41 ` David Hildenbrand
2021-01-20 11:58 ` Oscar Salvador
2021-01-20 11:58 ` Oscar Salvador
2021-01-21 9:23 ` Oscar Salvador
2021-01-21 9:23 ` Oscar Salvador
2021-01-22 9:18 ` David Hildenbrand
2021-01-22 9:18 ` David Hildenbrand
2021-01-22 10:41 ` Anshuman Khandual
2021-01-22 10:41 ` Anshuman Khandual
2021-01-22 10:42 ` David Hildenbrand
2021-01-22 10:42 ` David Hildenbrand
2021-01-22 10:43 ` David Hildenbrand
2021-01-22 10:43 ` David Hildenbrand
2021-01-18 13:13 ` [PATCH V3 2/3] arm64/mm: Define arch_get_mappable_range() Anshuman Khandual
2021-01-18 13:13 ` Anshuman Khandual
2021-01-19 12:24 ` David Hildenbrand
2021-01-19 12:24 ` David Hildenbrand
2021-01-18 13:13 ` [PATCH V3 3/3] s390/mm: " Anshuman Khandual
2021-01-18 13:13 ` Anshuman Khandual
2021-01-19 12:26 ` David Hildenbrand
2021-01-19 12:26 ` David Hildenbrand
2021-01-20 8:28 ` Anshuman Khandual
2021-01-20 8:28 ` Anshuman Khandual
2021-01-20 10:39 ` David Hildenbrand
2021-01-20 10:39 ` David Hildenbrand
2021-01-18 13:13 ` [PATCH RFC] virtio-mem: check against memhp_get_pluggable_range() which memory we can hotplug Anshuman Khandual
2021-01-18 13:13 ` Anshuman Khandual
2021-01-18 13:21 ` Anshuman Khandual
2021-01-18 13:21 ` Anshuman Khandual
2021-01-19 12:27 ` David Hildenbrand
2021-01-19 12:27 ` David Hildenbrand
2021-01-21 9:57 ` David Hildenbrand
2021-01-21 9:57 ` David Hildenbrand
2021-01-22 3:32 ` Anshuman Khandual
2021-01-22 3:32 ` Anshuman Khandual
2021-01-19 13:33 ` [PATCH V3 0/3] mm/memory_hotplug: Pre-validate the address range with platform David Hildenbrand
2021-01-19 13:33 ` David Hildenbrand
2021-01-19 13:40 ` Oscar Salvador [this message]
2021-01-19 13:40 ` Oscar Salvador
2021-01-20 8:37 ` Anshuman Khandual
2021-01-20 8:37 ` Anshuman Khandual
2021-01-22 6:04 ` Anshuman Khandual
2021-01-22 6:04 ` Anshuman Khandual
2021-01-22 8:34 ` David Hildenbrand
2021-01-22 8:34 ` 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=20210119134016.GA23408@linux \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.