On Tue, Aug 05, 2025 at 10:10:10PM +0200, Andy Shevchenko wrote: > On Tue, Aug 5, 2025 at 3:41 PM Askar Safin <[email protected]> wrote: > > ---- On Tue, 05 Aug 2025 17:00:45 +0400 Andy Shevchenko > > <[email protected]> wrote --- > > > Thanks for your report and the fix! My comments below. > > Andy, thank you for answer! I will write second version of my patch soon. > > Just to be clear, if you want all changes you listed, it should be a > patch series and not a single patch. > > > Also, please look at another my report: > > https://lore.kernel.org/regressions/[email protected]/ > > . > > Mario Limonciello said that we need you specially to proceed. > > Thanks for heads up. > > > > > 3. uint64_t a; printf ("%w64x", a); > > > > > > Haven't heard about it. Which C/POSIX/etc standard is this? > > Introduced in C23. https://www.c-language.org/ . > > https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3220.pdf , 7.23.6.1 > > A-ha, then it's definitely no, even if it compiles with all used > compilers. Too young a standard to follow.
It is a shame, as IMHO it's the nicest solution. But I agree that we need to support somewhat older standards. > > > > > * Laptop Dell Precision 7780 > > Side note: I bought this laptop, because it seems to be the only laptop in > > the world, > > which has ECC memory and in the same time doesn't have nvidia. > > Hmm... okay. > > -- > With Best Regards, > Andy Shevchenko >
