From: Greg KH <gregkh@linuxfoundation.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: will@kernel.org, catalin.marinas@arm.com, ryabinin.a.a@gmail.com,
andreyknvl@gmail.com, dvyukov@google.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
elver@google.com, akpm@linux-foundation.org,
kasan-dev@googlegroups.com
Subject: Re: [PATCH v4 0/3] arm64: support page mapping percpu first chunk allocator
Date: Thu, 16 Sep 2021 17:41:38 +0200 [thread overview]
Message-ID: <YUNlsgZoLG3g4Qup@kroah.com> (raw)
In-Reply-To: <c06faf6c-3d21-04f2-6855-95c86e96cf5a@huawei.com>
On Wed, Sep 15, 2021 at 04:33:09PM +0800, Kefeng Wang wrote:
> Hi Greg and Andrew， as Catalin saids，the series touches drivers/ and mm/
> but missing
>
> acks from both of you，could you take a look of this patchset(patch1 change
> mm/vmalloc.c
What patchset?
> and patch2 changes drivers/base/arch_numa.c).
that file is not really owned by anyone it seems :(
Can you provide a link to the real patch please?
thanks,
greg k-h
next prev parent reply other threads:[~2021-09-16 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 5:33 [PATCH v4 0/3] arm64: support page mapping percpu first chunk allocator Kefeng Wang
2021-09-10 5:33 ` [PATCH v4 1/3] vmalloc: Choose a better start address in vm_area_register_early() Kefeng Wang
2021-10-12 18:21 ` Catalin Marinas
2021-09-10 5:33 ` [PATCH v4 2/3] arm64: Support page mapping percpu first chunk allocator Kefeng Wang
2021-09-17 6:24 ` Greg KH
2021-09-17 6:55 ` Kefeng Wang
2021-09-17 7:04 ` Greg KH
2021-09-17 7:24 ` Kefeng Wang
2021-09-10 5:33 ` [PATCH v4 3/3] kasan: arm64: Fix pcpu_page_first_chunk crash with KASAN_VMALLOC Kefeng Wang
2021-10-12 18:17 ` Catalin Marinas
2021-10-13 1:09 ` Kefeng Wang
2021-09-15 8:33 ` [PATCH v4 0/3] arm64: support page mapping percpu first chunk allocator Kefeng Wang
2021-09-16 15:41 ` Greg KH [this message]
[not found] ` <525cb266-ecfc-284e-d701-4a8b40fe413b@huawei.com>
2021-09-17 6:24 ` Greg KH
2021-09-28 7:48 ` Kefeng Wang
2021-10-08 13:33 ` Kefeng Wang
2021-10-10 21:36 ` Andrew Morton
2021-10-11 1:09 ` Kefeng Wang
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=YUNlsgZoLG3g4Qup@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.com \
--cc=wangkefeng.wang@huawei.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