From: Catalin Marinas <catalin.marinas@arm.com>
To: Sudarshan Rajagopalan <sudaraja@codeaurora.org>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Gavin Shan <gshan@redhat.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Logan Gunthorpe <logang@deltatee.com>,
David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Price <steven.price@arm.com>
Subject: Re: [PATCH v4] arm64/mm: add fallback option to allocate virtually contiguous memory
Date: Fri, 6 Nov 2020 14:38:55 +0000 [thread overview]
Message-ID: <20201106143854.GH29329@gaia> (raw)
In-Reply-To: <4ca1e695f81b368a5487bdaa9b421a95@codeaurora.org>
On Wed, Nov 04, 2020 at 04:03:36PM -0800, Sudarshan Rajagopalan wrote:
> Did you have a chance to review this patch? It is reviewed by others and
> haven't seen any Nacks. This patch will be useful to have so that memory
> hotremove doesn't fail when such PMD_SIZE pages aren't available.. which is
> usually the case in low RAM devices.
Can you please post it again please with Will's ack? You posted a v4
which I think had the same message-id as v3. Mutt flagged it as
duplicate and I deleted it. Just to be sure (I'll queue it when we get
to -rc3).
Thanks.
--
Catalin
next prev parent reply other threads:[~2020-11-06 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 0:51 [PATCH v3] arm64/mm: add fallback option to allocate virtually contiguous memory Sudarshan Rajagopalan
2020-10-15 0:51 ` Sudarshan Rajagopalan
2020-10-15 8:36 ` Will Deacon
2020-10-16 18:49 ` Sudarshan Rajagopalan
2020-10-16 18:56 ` [PATCH v4] " Sudarshan Rajagopalan
2020-11-05 0:03 ` Sudarshan Rajagopalan
2020-11-06 14:38 ` Catalin Marinas [this message]
2020-11-06 13:43 ` Will Deacon
2020-10-16 18:56 ` Sudarshan Rajagopalan
2020-11-17 18:33 ` Catalin Marinas
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=20201106143854.GH29329@gaia \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@redhat.com \
--cc=gshan@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mark.rutland@arm.com \
--cc=steven.price@arm.com \
--cc=sudaraja@codeaurora.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox