From: Tong Tiangen <tongtiangen@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-riscv@lists.infradead.org>, <linux-arch@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Tong Tiangen <tongtiangen@huawei.com>,
<wangkefeng.wang@huawei.com>, Guohanjun <guohanjun@huawei.com>,
Xie XiuQi <xiexiuqi@huawei.com>
Subject: [PATCH -next 0/2] mm: fix some page table check related issues
Date: Tue, 17 May 2022 07:45:46 +0000 [thread overview]
Message-ID: <20220517074548.2227779-1-tongtiangen@huawei.com> (raw)
This patchset solves some ptc-related issues found recently.
Tong Tiangen (2):
riscv/mm: fix two page table check related issues
arm64/mm: fix page table check compile error for
CONFIG_PGTABLE_LEVELS=2
arch/arm64/include/asm/pgtable.h | 33 +++++++++++++++--------------
arch/riscv/include/asm/pgtable-64.h | 5 +++++
arch/riscv/include/asm/pgtable.h | 5 -----
include/asm-generic/pgtable-nopmd.h | 2 ++
4 files changed, 24 insertions(+), 21 deletions(-)
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Tong Tiangen <tongtiangen@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-riscv@lists.infradead.org>, <linux-arch@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Tong Tiangen <tongtiangen@huawei.com>,
<wangkefeng.wang@huawei.com>, Guohanjun <guohanjun@huawei.com>,
Xie XiuQi <xiexiuqi@huawei.com>
Subject: [PATCH -next 0/2] mm: fix some page table check related issues
Date: Tue, 17 May 2022 07:45:46 +0000 [thread overview]
Message-ID: <20220517074548.2227779-1-tongtiangen@huawei.com> (raw)
This patchset solves some ptc-related issues found recently.
Tong Tiangen (2):
riscv/mm: fix two page table check related issues
arm64/mm: fix page table check compile error for
CONFIG_PGTABLE_LEVELS=2
arch/arm64/include/asm/pgtable.h | 33 +++++++++++++++--------------
arch/riscv/include/asm/pgtable-64.h | 5 +++++
arch/riscv/include/asm/pgtable.h | 5 -----
include/asm-generic/pgtable-nopmd.h | 2 ++
4 files changed, 24 insertions(+), 21 deletions(-)
--
2.25.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Tong Tiangen <tongtiangen@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-riscv@lists.infradead.org>, <linux-arch@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Tong Tiangen <tongtiangen@huawei.com>,
<wangkefeng.wang@huawei.com>, Guohanjun <guohanjun@huawei.com>,
Xie XiuQi <xiexiuqi@huawei.com>
Subject: [PATCH -next 0/2] mm: fix some page table check related issues
Date: Tue, 17 May 2022 07:45:46 +0000 [thread overview]
Message-ID: <20220517074548.2227779-1-tongtiangen@huawei.com> (raw)
This patchset solves some ptc-related issues found recently.
Tong Tiangen (2):
riscv/mm: fix two page table check related issues
arm64/mm: fix page table check compile error for
CONFIG_PGTABLE_LEVELS=2
arch/arm64/include/asm/pgtable.h | 33 +++++++++++++++--------------
arch/riscv/include/asm/pgtable-64.h | 5 +++++
arch/riscv/include/asm/pgtable.h | 5 -----
include/asm-generic/pgtable-nopmd.h | 2 ++
4 files changed, 24 insertions(+), 21 deletions(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-05-17 7:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 7:45 Tong Tiangen [this message]
2022-05-17 7:45 ` [PATCH -next 0/2] mm: fix some page table check related issues Tong Tiangen
2022-05-17 7:45 ` Tong Tiangen
2022-05-17 7:45 ` [PATCH -next 1/2] riscv/mm: fix two " Tong Tiangen
2022-05-17 7:45 ` Tong Tiangen
2022-05-17 7:45 ` Tong Tiangen
2022-05-17 7:45 ` [PATCH -next 2/2] arm64/mm: fix page table check compile error for CONFIG_PGTABLE_LEVELS=2 Tong Tiangen
2022-05-17 7:45 ` Tong Tiangen
2022-05-17 7:45 ` Tong Tiangen
2022-05-18 16:28 ` Catalin Marinas
2022-05-18 16:28 ` Catalin Marinas
2022-05-18 16:28 ` Catalin Marinas
2022-05-18 17:13 ` Andrew Morton
2022-05-18 17:13 ` Andrew Morton
2022-05-18 17:13 ` Andrew Morton
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=20220517074548.2227779-1-tongtiangen@huawei.com \
--to=tongtiangen@huawei.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=xiexiuqi@huawei.com \
/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.