From: Tang Yizhou <tangyizhou@huawei.com>
To: Nicholas Piggin <npiggin@gmail.com>, <linux-mm@kvack.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "Borislav Petkov" <bp@alien8.de>,
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Zefan Li <lizefan@huawei.com>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
<john.wanghui@huawei.com>
Subject: Re: [PATCH v4 6/8] mm: Move vmap_range from lib/ioremap.c to mm/vmalloc.c
Date: Mon, 17 Aug 2020 21:23:51 +0800 [thread overview]
Message-ID: <27dd4db0-00e1-383a-f276-1622b2e68a4d@huawei.com> (raw)
In-Reply-To: <20200816090904.83947-7-npiggin@gmail.com>
Hi Nicholas,
We may change the title as follows:
mm: Move vmap_range from mm/ioremap.c to mm/vmalloc.c
Yizhou
next prev parent reply other threads:[~2020-08-17 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 9:08 [PATCH v4 0/8] huge vmalloc mappings Nicholas Piggin
2020-08-16 9:08 ` [PATCH v4 1/8] mm/vmalloc: fix vmalloc_to_page for huge vmap mappings Nicholas Piggin
2020-08-16 9:08 ` [PATCH v4 2/8] mm: apply_to_pte_range warn and fail if a large pte is encountered Nicholas Piggin
2020-08-16 9:08 ` [PATCH v4 3/8] mm/vmalloc: rename vmap_*_range vmap_pages_*_range Nicholas Piggin
2020-08-16 9:09 ` [PATCH v4 4/8] lib/ioremap: rename ioremap_*_range to vmap_*_range Nicholas Piggin
2020-08-16 9:09 ` [PATCH v4 5/8] mm: HUGE_VMAP arch support cleanup Nicholas Piggin
2020-08-16 9:09 ` [PATCH v4 6/8] mm: Move vmap_range from lib/ioremap.c to mm/vmalloc.c Nicholas Piggin
2020-08-17 13:23 ` Tang Yizhou [this message]
2020-08-16 9:09 ` [PATCH v4 7/8] mm/vmalloc: add vmap_range_noflush variant Nicholas Piggin
2020-08-16 9:09 ` [PATCH v4 8/8] mm/vmalloc: Hugepage vmalloc mappings Nicholas Piggin
2020-08-18 0:30 ` [mm/vmalloc] a1a514f208: WARNING:at_kernel/locking/lockdep.c:#__lock_acquire kernel test robot
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=27dd4db0-00e1-383a-f276-1622b2e68a4d@huawei.com \
--to=tangyizhou@huawei.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=hpa@zytor.com \
--cc=john.wanghui@huawei.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=npiggin@gmail.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@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