From: Ryan Roberts <ryan.roberts@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/mm: Drop PMD_SECT_VALID
Date: Wed, 24 Jul 2024 08:52:39 +0100 [thread overview]
Message-ID: <8f6b7735-5746-4bd0-b248-677638d54c7c@arm.com> (raw)
In-Reply-To: <20240724044712.602210-1-anshuman.khandual@arm.com>
On 24/07/2024 05:47, Anshuman Khandual wrote:
> This just drops off the macro PMD_SECT_VALID which remains unused. Because
> macro PMD_TYPE_SECT with same value (_AT(pmdval_t, 1) << 0), gets used for
> creating or updating given block mappings.
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Ryan Roberts <ryan.roberts@arm.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
Reviewed-by: Ryan Roberts <ryan.roberts@arm.com>
> ---
> arch/arm64/include/asm/pgtable-hwdef.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm64/include/asm/pgtable-hwdef.h b/arch/arm64/include/asm/pgtable-hwdef.h
> index 1f60aa1bc750..86e803ea8885 100644
> --- a/arch/arm64/include/asm/pgtable-hwdef.h
> +++ b/arch/arm64/include/asm/pgtable-hwdef.h
> @@ -135,7 +135,6 @@
> /*
> * Section
> */
> -#define PMD_SECT_VALID (_AT(pmdval_t, 1) << 0)
> #define PMD_SECT_USER (_AT(pmdval_t, 1) << 6) /* AP[1] */
> #define PMD_SECT_RDONLY (_AT(pmdval_t, 1) << 7) /* AP[2] */
> #define PMD_SECT_S (_AT(pmdval_t, 3) << 8)
next prev parent reply other threads:[~2024-07-24 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 4:47 Anshuman Khandual
2024-07-24 7:52 ` Ryan Roberts [this message]
2024-08-16 15:15 ` Will Deacon
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=8f6b7735-5746-4bd0-b248-677638d54c7c@arm.com \
--to=ryan.roberts@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®