From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Don't use QEMU_VERSION in ATA/ATAPI replies to IDENTIFY cmds
Date: Thu, 11 Sep 2008 14:58:55 +0100 [thread overview]
Message-ID: <200809111458.57906.paul@codesourcery.com> (raw)
In-Reply-To: <20080911115629.GA16427@shareable.org>
> Bug fixes and performance improvements are fine.
The whole point of the drive firmware version is that it's supposed to change
every time bug fixes and performance improvements are made. I'm pretty sure
it'll also change when you upgrade the firmware on a real drive.
As far as I'm concerned anything that relies on this value being constant over
qemu is just plain broken.
Paul
next prev parent reply other threads:[~2008-09-11 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 0:19 [Qemu-devel] [PATCH] Don't use QEMU_VERSION in ATA/ATAPI replies to IDENTIFY cmds Marc Bevand
2008-09-11 0:30 ` Anthony Liguori
2008-09-11 1:19 ` Marc Bevand
2008-09-11 1:40 ` Glauber Costa
2008-09-11 3:34 ` Marc Bevand
2008-09-11 8:18 ` Jamie Lokier
2008-09-11 11:44 ` Glauber Costa
2008-09-11 11:56 ` Jamie Lokier
2008-09-11 13:58 ` Paul Brook [this message]
2008-09-11 14:11 ` Avi Kivity
2008-09-11 15:16 ` Ian Kirk
2008-09-11 15:55 ` Paul Brook
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=200809111458.57906.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).