From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Petr Mladek <pmladek@suse.com>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-mm@kvack.org, usama.arif@linux.dev, hughd@google.com,
willy@infradead.org, ryan.roberts@arm.com,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] mm: Standardize printing for pgtable entries
Date: Thu, 9 Jul 2026 12:24:08 +0200 [thread overview]
Message-ID: <a23c0ace-b52c-4f28-9f40-d0b6dc4ca2d3@kernel.org> (raw)
In-Reply-To: <ak90WW3I4tmg7Pwz@ashevche-desk.local>
On 7/9/26 12:13, Andy Shevchenko wrote:
> On Thu, Jul 09, 2026 at 01:11:46PM +0300, Andy Shevchenko wrote:
>> On Thu, Jul 09, 2026 at 11:15:27AM +0200, Petr Mladek wrote:
>
> ...
>
>>> But maybe you had something particular in mind.
>>
>> Yes, I was thinking of a wrapper on top of special_hex_number(). It takes size
>> as an argument and hence will work even for 128-bit cases.
>
> Okay, the argument is limited to 64-bit in there. But I don't think it's a big
> impediment.
Rewrite number() / create a new 128bit variants to avoid 3 simple snprintf()
statements? :)
Hm ...
--
Cheers,
David
next prev parent reply other threads:[~2026-07-09 10:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 4:43 [PATCH V3] mm: Standardize printing for pgtable entries Anshuman Khandual
2026-07-09 7:40 ` Andy Shevchenko
2026-07-09 9:12 ` David Hildenbrand (Arm)
2026-07-09 10:09 ` Andy Shevchenko
2026-07-09 10:19 ` David Hildenbrand (Arm)
2026-07-09 9:15 ` Petr Mladek
2026-07-09 10:11 ` Andy Shevchenko
2026-07-09 10:13 ` Andy Shevchenko
2026-07-09 10:24 ` David Hildenbrand (Arm) [this message]
2026-07-09 10:43 ` Andy Shevchenko
2026-07-09 11:12 ` Anshuman Khandual
2026-07-09 11:54 ` Andy Shevchenko
2026-07-10 0:08 ` Andrew Morton
2026-07-10 3:10 ` Anshuman Khandual
2026-07-10 3:32 ` Andrew Morton
2026-07-10 8:16 ` David Hildenbrand (Arm)
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=a23c0ace-b52c-4f28-9f40-d0b6dc4ca2d3@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pmladek@suse.com \
--cc=ryan.roberts@arm.com \
--cc=usama.arif@linux.dev \
--cc=willy@infradead.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