From: Tyrel Datwyler <tyreld@linux.ibm.com>
To: Laurent Dufour <ldufour@linux.ibm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org
Cc: nathanl@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] pseries/drmem: update LMBs after LPM
Date: Mon, 3 May 2021 13:44:08 -0700 [thread overview]
Message-ID: <bdc510ff-f9f6-b032-0f0d-52a274fb9dab@linux.ibm.com> (raw)
In-Reply-To: <1eac9540-e8b4-53be-1f27-4c36f92c8a5e@linux.ibm.com>
On 5/3/21 10:28 AM, Laurent Dufour wrote:
> Le 01/05/2021 à 01:58, Tyrel Datwyler a écrit :
>> On 4/30/21 9:13 AM, Laurent Dufour wrote:
>>> Le 29/04/2021 à 21:12, Tyrel Datwyler a écrit :
>>>> On 4/29/21 3:27 AM, Aneesh Kumar K.V wrote:
>>>>> Laurent Dufour <ldufour@linux.ibm.com> writes:
>>>>>
Snip
>>
>> As of today I don't have a problem with your patch. This was more of me pointing
>> out things that I think are currently wrong with our memory hotplug
>> implementation, and that we need to take a long hard look at it down the road.
>
> I do agree, there is a lot of odd things there to address in this area.
> If you're ok with that patch, do you mind to add a reviewed-by?
>
Can you send a v4 with the fix for the duplicate update included?
-Tyrel
next prev parent reply other threads:[~2021-05-03 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 9:47 [PATCH v3] pseries/drmem: update LMBs after LPM Laurent Dufour
2021-04-29 10:27 ` Aneesh Kumar K.V
2021-04-29 11:31 ` Laurent Dufour
2021-04-29 11:35 ` Laurent Dufour
2021-04-29 12:38 ` Laurent Dufour
2021-04-29 19:12 ` Tyrel Datwyler
2021-04-30 16:13 ` Laurent Dufour
2021-04-30 23:58 ` Tyrel Datwyler
2021-05-03 17:28 ` Laurent Dufour
2021-05-03 20:44 ` Tyrel Datwyler [this message]
2021-05-04 7:03 ` Laurent Dufour
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=bdc510ff-f9f6-b032-0f0d-52a274fb9dab@linux.ibm.com \
--to=tyreld@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nathanl@linux.ibm.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).