From: Catalin Marinas <catalin.marinas@arm.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: will@kernel.org, ryabinin.a.a@gmail.com, andreyknvl@gmail.com,
dvyukov@google.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
linux-mm@kvack.org, elver@google.com,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v3 0/3] arm64: support page mapping percpu first chunk allocator
Date: Wed, 25 Aug 2021 19:11:13 +0100 [thread overview]
Message-ID: <20210825181112.GK3420@arm.com> (raw)
In-Reply-To: <9b75f4e5-a675-1227-0476-43fc21509086@huawei.com>
On Thu, Aug 12, 2021 at 02:07:36PM +0800, Kefeng Wang wrote:
> The drivers/base/arch_numa.c is only shared by riscv and arm64,
>
> and the change from patch2 won't broke riscv.
>
> Could all patches be merged by arm64 tree? or any new comments?
The series touches drivers/ and mm/ but missing acks from both Greg and
Andrew (cc'ing them).
I'm also happy for the series to go in via the mm tree in case Andrew
wants to take it.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: will@kernel.org, ryabinin.a.a@gmail.com, andreyknvl@gmail.com,
dvyukov@google.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
linux-mm@kvack.org, elver@google.com,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v3 0/3] arm64: support page mapping percpu first chunk allocator
Date: Wed, 25 Aug 2021 19:11:13 +0100 [thread overview]
Message-ID: <20210825181112.GK3420@arm.com> (raw)
In-Reply-To: <9b75f4e5-a675-1227-0476-43fc21509086@huawei.com>
On Thu, Aug 12, 2021 at 02:07:36PM +0800, Kefeng Wang wrote:
> The drivers/base/arch_numa.c is only shared by riscv and arm64,
>
> and the change from patch2 won't broke riscv.
>
> Could all patches be merged by arm64 tree? or any new comments?
The series touches drivers/ and mm/ but missing acks from both Greg and
Andrew (cc'ing them).
I'm also happy for the series to go in via the mm tree in case Andrew
wants to take it.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-25 18:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 9:37 [PATCH v3 0/3] arm64: support page mapping percpu first chunk allocator Kefeng Wang
2021-08-09 9:37 ` Kefeng Wang
2021-08-09 9:37 ` [PATCH v3 1/3] vmalloc: Choose a better start address in vm_area_register_early() Kefeng Wang
2021-08-09 9:37 ` Kefeng Wang
2021-08-25 17:59 ` Catalin Marinas
2021-08-25 17:59 ` Catalin Marinas
2021-08-27 8:36 ` Kefeng Wang
2021-08-27 8:36 ` Kefeng Wang
2021-08-09 9:37 ` [PATCH v3 2/3] arm64: Support page mapping percpu first chunk allocator Kefeng Wang
2021-08-09 9:37 ` Kefeng Wang
2021-08-25 18:08 ` Catalin Marinas
2021-08-25 18:08 ` Catalin Marinas
2021-08-09 9:37 ` [PATCH v3 3/3] kasan: arm64: Fix pcpu_page_first_chunk crash with KASAN_VMALLOC Kefeng Wang
2021-08-09 9:37 ` Kefeng Wang
2021-08-09 11:10 ` Kefeng Wang
2021-08-09 11:10 ` Kefeng Wang
2021-08-09 11:21 ` Marco Elver
2021-08-09 11:21 ` Marco Elver
2021-08-09 11:21 ` Marco Elver
2021-08-09 13:34 ` Kefeng Wang
2021-08-09 13:34 ` Kefeng Wang
2021-08-09 18:21 ` Andrey Konovalov
2021-08-09 18:21 ` Andrey Konovalov
2021-08-09 18:21 ` Andrey Konovalov
2021-08-12 6:07 ` [PATCH v3 0/3] arm64: support page mapping percpu first chunk allocator Kefeng Wang
2021-08-12 6:07 ` Kefeng Wang
2021-08-23 2:29 ` Kefeng Wang
2021-08-23 2:29 ` Kefeng Wang
2021-08-25 18:11 ` Catalin Marinas [this message]
2021-08-25 18:11 ` 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=20210825181112.GK3420@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.