[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d992d4a-1aea-42a7-aa79-4ede80293f9b@infradead.org>
Date: Wed, 28 Jan 2026 11:12:31 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: David Matlack <dmatlack@...gle.com>, Ted Logan <tedlogan@...com>
Cc: Alex Williamson <alex@...zbot.org>, Shuah Khan <shuah@...nel.org>,
Raghavendra Rao Ananta <rananta@...gle.com>, Alex Mastro <amastro@...com>,
kvm@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] vfio: selftests: fix format conversion compiler warning
On 1/28/26 11:06 AM, David Matlack wrote:
> On Wed, Jan 28, 2026 at 10:38 AM Ted Logan <tedlogan@...com> wrote:
>>
>> Use the standard format conversion macro PRIx64 to generate the
>> appropriate format conversion for 64-bit integers. Fixes a compiler
>> warning with -Wformat on i386.
>>
>> Signed-off-by: Ted Logan <tedlogan@...com>
>> Reported-by: kernel test robot <lkp@...el.com>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202601211830.aBEjmEFD-lkp@intel.com/
>
> Thanks for the patch.
>
> I've been seeing these i386 reports as well. I find the PRIx64, etc.
> format specifiers make format strings very hard to read. And I think
> there were some other issues when building VFIO selftests with i386
> the last time I tried.
>
> I was thinking instead we should just not support i386 builds of VFIO
> selftests. But I hadn't gotten around to figuring out the right
> Makefile magic to make that happen.
There are other 32-bit CPUs besides i386.
Or do only support X86?
--
~Randy
Powered by blists - more mailing lists