From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
suzuki.poulose@arm.com, linux-kernel@vger.kernel.org,
mark.rutland@arm.com
Subject: Re: [PATCH V2] arm64/mm: Add pud_sect_supported()
Date: Wed, 29 Sep 2021 18:48:23 +0100 [thread overview]
Message-ID: <163293087332.927113.5526863542809374103.b4-ty@kernel.org> (raw)
In-Reply-To: <1632130171-472-1-git-send-email-anshuman.khandual@arm.com>
On Mon, 20 Sep 2021 14:59:31 +0530, Anshuman Khandual wrote:
> Section mapping at PUD level is supported only on 4K pages and currently it
> gets verified with explicit #ifdef or IS_ENABLED() constructs. This adds a
> new helper pud_sect_supported() for this purpose, which particularly cleans
> up the HugeTLB code path. It updates relevant switch statements with checks
> for __PAGETABLE_PMD_FOLDED in order to avoid build failures caused with two
> identical switch case values in those code blocks.
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64/mm: Add pud_sect_supported()
https://git.kernel.org/arm64/c/f8b46c4b51ab
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-09-29 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 9:29 Anshuman Khandual
2021-09-20 15:41 ` Catalin Marinas
2021-09-22 4:44 ` Anshuman Khandual
2021-09-22 4:52 ` Itaru Kitayama
2021-09-22 5:07 ` Anshuman Khandual
2021-09-22 9:52 ` Catalin Marinas
2021-09-29 17:48 ` Will Deacon [this message]
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=163293087332.927113.5526863542809374103.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®