From: Anshuman Khandual <anshuman.khandual@arm.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
Will Deacon <will@kernel.org>, Mike Rapoport <rppt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/mm: Rename ptdesc_t
Date: Wed, 20 May 2026 07:38:50 +0530 [thread overview]
Message-ID: <2f60361d-43b9-4f7f-b786-7852d081f4a1@arm.com> (raw)
In-Reply-To: <34c31f7a-e3e5-47c1-9e41-e6e9a90e89d3@kernel.org>
On 19/05/26 4:32 PM, David Hildenbrand (Arm) wrote:
> On 5/19/26 12:44, Will Deacon wrote:
>> On Thu, Apr 30, 2026 at 09:51:46AM +0200, Mike Rapoport wrote:
>>> Hi Anshuman,
>>>
>>> On Thu, Apr 30, 2026 at 04:49:33AM +0100, Anshuman Khandual wrote:
>>>> ptdesc_t sounds very similar to the core MM struct ptdesc which is actually
>>>> the memory descriptor for page table allocations. Hence rename this typedef
>>>> element as pxxval_t instead for better clarity and separation.
>>>
>>> Maybe we should keep the "pt" prefix and make it "ptval_t"?
>>
>> Yeah, the 'pxx' prefix really hurts my eyes. Please use something else!
>
> Fine with me as long as we don't call it something with "pte" in it.
>
Seems like there are two choices here
(A) pxdval_t
(B) ptval_t which Mike had suggested earlier
Unless there is a preference will probably go with pxdval_t
next prev parent reply other threads:[~2026-05-20 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 3:49 Anshuman Khandual
2026-04-30 7:51 ` Mike Rapoport
2026-05-19 10:44 ` Will Deacon
2026-05-19 11:02 ` David Hildenbrand (Arm)
2026-05-20 2:08 ` Anshuman Khandual [this message]
2026-05-20 5:26 ` David Hildenbrand (Arm)
2026-05-20 5:38 ` Anshuman Khandual
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=2f60361d-43b9-4f7f-b786-7852d081f4a1@arm.com \
--to=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@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®