[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2e7b74ad-b308-46af-9edb-59c0ce416d89@roeck-us.net>
Date: Sun, 22 Jun 2025 17:39:22 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Pratyush Yadav <pratyush@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Alexander Usyskin <alexander.usyskin@...el.com>,
Miquel Raynal <miquel.raynal@...tlin.com>
Subject: Re: Linux 6.16-rc1
On Sat, Jun 21, 2025 at 08:59:46AM -0700, Linus Torvalds wrote:
> On Sat, 21 Jun 2025 at 05:44, Pratyush Yadav <pratyush@...nel.org> wrote:
> >
> > I don't have much idea of how people use qemu for testing, but since you
> > say this is important for testing workloads, I can take a deeper dive
> > next week and have an answer by -rc4.
>
> Thanks. I'm not sure *how* important this is, but if it affects
> Guenter's test coverage, I assume it affects others too.
>
> But it's not entirely clear how much it *does* affect Guenter. He says
> five failed tests, but those are all accounted for by the master
> device thing.
>
> Guenter, maybe you can clarify?
>
Sorry for the delay; I was travelling.
I modified qemu to make the flash type configurable, so it is not a problem
for me. However, anyone using upstream qemu will see the problem. My qemu patch
adding the option to configure the flash type was rejected, so those affected
will have to wait for a proper qemu fix.
I would suggest to not make any changes in the kernel: The qemu problems should be
fixed in qemu. I only brought this up to raise awareness that there is a qemu related
problem, not to ask for a change in the Linux kernel.
Guenter
Powered by blists - more mailing lists