From: Zhenyu Ye <yezhenyu2@huawei.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
<catalin.marinas@arm.com>, <peterz@infradead.org>,
<mark.rutland@arm.com>, <will@kernel.org>,
<aneesh.kumar@linux.ibm.com>, <akpm@linux-foundation.org>,
<npiggin@gmail.com>, <arnd@arndb.de>, <rostedt@goodmis.org>,
<maz@kernel.org>, <suzuki.poulose@arm.com>, <tglx@linutronix.de>,
<yuzhao@google.com>, <Dave.Martin@arm.com>,
<steven.price@arm.com>, <broonie@kernel.org>,
<guohanjun@huawei.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>,
<linux-mm@kvack.org>, <arm@kernel.org>, <xiexiangyou@huawei.com>,
<prime.zeng@hisilicon.com>, <zhangshaokun@hisilicon.com>,
<kuhn.chenqun@huawei.com>
Subject: Re: [PATCH v3 1/6] arm64: Detect the ARMv8.4 TTL feature
Date: Tue, 26 May 2020 14:40:38 +0800 [thread overview]
Message-ID: <050b7ee6-c7aa-5d61-4dff-4792a411464e@huawei.com> (raw)
In-Reply-To: <c6b6eb07-2606-9fc0-280a-e53b81a6491c@arm.com>
Hi Anshuman,
On 2020/5/26 10:39, Anshuman Khandual wrote:
> This patch (https://patchwork.kernel.org/patch/11557359/) is adding some
> more ID_AA64MMFR2 features including the TTL. I am going to respin parts
> of the V4 series patches along with the above mentioned patch. So please
> rebase this series accordingly, probably on latest next.
>
I noticed that some patches of your series have been merged into arm64
tree (for-next/cpufeature), such as TLB range, but this one not. Why?
BTW, this patch is provided by Marc in his NV series [1], maybe you
should also let him know.
I will rebase my series after your patch is merged.
[1] https://lore.kernel.org/linux-arm-kernel/d6032191-ba0e-82a4-4dde-11beef369a11@arm.com/
Thanks,
Zhenyu
next prev parent reply other threads:[~2020-05-26 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 12:52 [PATCH v3 0/6] arm64: tlb: add support for " Zhenyu Ye
2020-05-25 12:52 ` [PATCH v3 1/6] arm64: Detect the ARMv8.4 " Zhenyu Ye
2020-05-26 2:39 ` Anshuman Khandual
2020-05-26 6:40 ` Zhenyu Ye [this message]
2020-05-26 10:06 ` Marc Zyngier
2020-05-25 12:52 ` [PATCH v3 2/6] arm64: Add level-hinted TLB invalidation helper Zhenyu Ye
2020-05-25 12:52 ` [PATCH v3 3/6] arm64: Add tlbi_user_level " Zhenyu Ye
2020-05-25 12:52 ` [PATCH v3 4/6] tlb: mmu_gather: add tlb_flush_*_range APIs Zhenyu Ye
2020-05-25 12:52 ` [PATCH v3 5/6] mm: tlb: Provide flush_*_tlb_range wrappers Zhenyu Ye
2020-05-25 12:53 ` [PATCH v3 6/6] arm64: tlb: Set the TTL field in flush_tlb_range Zhenyu Ye
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=050b7ee6-c7aa-5d61-4dff-4792a411464e@huawei.com \
--to=yezhenyu2@huawei.com \
--cc=Dave.Martin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anshuman.khandual@arm.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=kuhn.chenqun@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=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=prime.zeng@hisilicon.com \
--cc=rostedt@goodmis.org \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=xiexiangyou@huawei.com \
--cc=yuzhao@google.com \
--cc=zhangshaokun@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox