linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tang Yizhou <tangyizhou@huawei.com>
To: Nicholas Piggin <npiggin@gmail.com>, <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>,
	Zefan Li <lizefan@huawei.com>,
	Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
	Christoph Hellwig <hch@infradead.org>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "Borislav Petkov" <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v7 05/12] mm: HUGE_VMAP arch support cleanup
Date: Fri, 11 Sep 2020 18:36:36 +0800	[thread overview]
Message-ID: <534a0d5e-3a6f-c8e5-38f9-7e24662acb31@huawei.com> (raw)
In-Reply-To: <20200825145753.529284-6-npiggin@gmail.com>

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().


  reply	other threads:[~2020-09-11 10:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 14:57 [PATCH v7 00/12] huge vmalloc mappings Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 01/12] mm/vmalloc: fix vmalloc_to_page for huge vmap mappings Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 02/12] mm: apply_to_pte_range warn and fail if a large pte is encountered Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 03/12] mm/vmalloc: rename vmap_*_range vmap_pages_*_range Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 04/12] mm/ioremap: rename ioremap_*_range to vmap_*_range Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 05/12] mm: HUGE_VMAP arch support cleanup Nicholas Piggin
2020-09-11 10:36   ` Tang Yizhou [this message]
2020-09-14  1:49     ` Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 06/12] powerpc: inline huge vmap supported functions Nicholas Piggin
2020-08-26 11:59   ` Michael Ellerman
2020-08-25 14:57 ` [PATCH v7 07/12] arm64: " Nicholas Piggin
2020-08-26 10:02   ` Catalin Marinas
2020-08-25 14:57 ` [PATCH v7 08/12] x86: " Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 09/12] mm: Move vmap_range from mm/ioremap.c to mm/vmalloc.c Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 10/12] mm/vmalloc: add vmap_range_noflush variant Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 11/12] mm/vmalloc: Hugepage vmalloc mappings Nicholas Piggin
2020-08-25 14:57 ` [PATCH v7 12/12] powerpc/64s/radix: Enable huge " Nicholas Piggin

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=534a0d5e-3a6f-c8e5-38f9-7e24662acb31@huawei.com \
    --to=tangyizhou@huawei.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=npiggin@gmail.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).