public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: "liwei (CM)" <liwei213@huawei.com>
Cc: "Song Bao Hua (Barry Song)" <song.bao.hua@hisilicon.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	"will@kernel.org" <will@kernel.org>,
	"Xiaqing (A)" <saberlily.xia@hisilicon.com>,
	"Chenfeng (puck)" <puck.chen@hisilicon.com>,
	butao <butao@hisilicon.com>,
	fengbaopeng <fengbaopeng2@hisilicon.com>,
	"nsaenzjulienne@suse.de" <nsaenzjulienne@suse.de>,
	"steve.capper@arm.com" <steve.capper@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	sujunfei <sujunfei2@hisilicon.com>,
	Linuxarm <linuxarm@huawei.com>
Subject: Re: 答复: [PATCH v2] arm64: mm: free unused memmap for sparse memory model that define VMEMMAP
Date: Mon, 16 Nov 2020 10:46:31 +0000	[thread overview]
Message-ID: <X7JYhyr2a4H6D+cQ@trantor> (raw)
In-Reply-To: <f34d3387368a406582bce36627cdc29c@huawei.com>

On Mon, Nov 16, 2020 at 08:42:17AM +0000, liwei (CM) wrote:
> I have changed SECTION_SIZE_BITS to 27 in our products, but I don't
> have to submit it.

Well, if you send a patch, I'm happy to merge it.

-- 
Catalin

  reply	other threads:[~2020-11-16 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12  1:06 [PATCH v2] arm64: mm: free unused memmap for sparse memory model that define VMEMMAP Wei Li
2020-08-17  8:04 ` Mike Rapoport
2020-09-03 12:05   ` Catalin Marinas
2020-09-03 12:27     ` Mike Rapoport
2020-11-16  8:33     ` Song Bao Hua (Barry Song)
2020-11-16  8:42       ` 答复: " liwei (CM)
2020-11-16 10:46         ` Catalin Marinas [this message]
2020-11-23  3:45           ` 答复: " liwei (CM)

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=X7JYhyr2a4H6D+cQ@trantor \
    --to=catalin.marinas@arm.com \
    --cc=butao@hisilicon.com \
    --cc=fengbaopeng2@hisilicon.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liwei213@huawei.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=puck.chen@hisilicon.com \
    --cc=rppt@linux.ibm.com \
    --cc=saberlily.xia@hisilicon.com \
    --cc=song.bao.hua@hisilicon.com \
    --cc=steve.capper@arm.com \
    --cc=sujunfei2@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox