From: Pratyush Yadav <pratyush@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Pratyush Yadav <pratyush@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: Linux 6.16-rc1
Date: Mon, 23 Jun 2025 13:17:27 +0200 [thread overview]
Message-ID: <mafs0wm92u2pk.fsf@kernel.org> (raw)
In-Reply-To: <2e7b74ad-b308-46af-9edb-59c0ce416d89@roeck-us.net>
On Sun, Jun 22 2025, Guenter Roeck wrote:
> On Sat, Jun 21, 2025 at 08:59:46AM -0700, Linus Torvalds wrote:
>> On Sat, 21 Jun 2025 at 05:44, Pratyush Yadav <pratyush@kernel.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.
In case you missed it, see my reply in [0]. For me the flash works fine
with qemu v10.0.0. Which version do you have?
Anyway, I agree with you. Without further evidence, I think the kernel
side is fine and no fixes should be needed.
[0] https://lore.kernel.org/linux-mtd/mafs01prbvbjm.fsf@kernel.org/
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2025-06-23 11:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 21:17 Linux 6.16-rc1 Linus Torvalds
2025-06-11 1:25 ` Guenter Roeck
2025-06-21 5:42 ` Linus Torvalds
2025-06-21 12:44 ` Pratyush Yadav
2025-06-21 15:59 ` Linus Torvalds
2025-06-23 0:39 ` Guenter Roeck
2025-06-23 11:17 ` Pratyush Yadav [this message]
2025-06-23 13:47 ` Guenter Roeck
2025-06-11 5:55 ` linux-next: stats (Was: Linux 6.16-rc1) Stephen Rothwell
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=mafs0wm92u2pk.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=alexander.usyskin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=miquel.raynal@bootlin.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.