From: Nicholas Piggin <npiggin@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Tang Yizhou <tangyizhou@huawei.com>
Cc: linux-arch@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Christoph Hellwig <hch@infradead.org>,
Zefan Li <lizefan@huawei.com>, Borislav Petkov <bp@alien8.de>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will@kernel.org>, Ingo Molnar <mingo@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 05/12] mm: HUGE_VMAP arch support cleanup
Date: Mon, 14 Sep 2020 11:49:22 +1000 [thread overview]
Message-ID: <1600048125.6soarrvq20.astroid@bobo.none> (raw)
In-Reply-To: <534a0d5e-3a6f-c8e5-38f9-7e24662acb31@huawei.com>
Excerpts from Tang Yizhou's message of September 11, 2020 8:36 pm:
> On 2020/8/25 22:57, Nicholas Piggin wrote:
>> -int __init arch_ioremap_pud_supported(void)
>> +bool arch_vmap_pud_supported(pgprot_t prot);
>> {
>> /*
>> * Only 4k granule supports level 1 block mappings.
>> @@ -1319,9 +1319,9 @@ int __init arch_ioremap_pud_supported(void)
>> !IS_ENABLED(CONFIG_PTDUMP_DEBUGFS);
>> }
>
> There is a compilation error because of the redundant semicolon at arch_vmap_pud_supported().
Huh thanks, I didn't see that for some reason.
I'll fix it up and re-send.
Thanks,
Nick
_______________________________________________
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:[~2020-09-14 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200825145753.529284-1-npiggin@gmail.com>
2020-08-25 14:57 ` [PATCH v7 05/12] mm: HUGE_VMAP arch support cleanup Nicholas Piggin
2020-09-11 10:36 ` Tang Yizhou
2020-09-14 1:49 ` Nicholas Piggin [this message]
2020-08-25 14:57 ` [PATCH v7 07/12] arm64: inline huge vmap supported functions Nicholas Piggin
2020-08-26 10:02 ` 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=1600048125.6soarrvq20.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=hch@infradead.org \
--cc=hpa@zytor.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=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=tangyizhou@huawei.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).