[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aFqjje91QnAgg2_h@smile.fi.intel.com>
Date: Tue, 24 Jun 2025 16:09:33 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Anshuman Khandual <anshuman.khandual@....com>, linux-mm@...ck.org,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
Jonathan Corbet <corbet@....net>,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [RFC 1/2] lib/vsprintf: Add support for pte_t
On Tue, Jun 24, 2025 at 12:48:58PM +0200, Petr Mladek wrote:
> On Fri 2025-06-20 13:32:31, Anshuman Khandual wrote:
> > On 19/06/25 7:31 PM, Petr Mladek wrote:
...
> > Something like BUILD_BUG_ON() against pte_t as either u64 or u32 aka all
> > the sizes the print format is going to support and it should pass on all
> > platforms ?
>
> Yes, I had BUILD_BUG_ON() in mind. It would be nice if you check at
> least the most known architectures.
FWIW, we use static_assert():s in the file, so may be better to use them.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists