From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Wang Cheng Yeh <cywang.eda@gmail.com>
Subject: Re: [Qemu-devel] scsi interface patch
Date: Sun, 22 Apr 2007 14:54:25 +0100 [thread overview]
Message-ID: <200704221454.27190.paul@codesourcery.com> (raw)
In-Reply-To: <a20f395e0704211901r52c39000y3db6be74e6854175@mail.gmail.com>
On Sunday 22 April 2007 03:01, Wang Cheng Yeh wrote:
> The number of responded bytes from scsi device do not match the expected
> value of lsi53c895a driver. hence, the mismatch interrupt happen, but the
> driver does not always handle it correctly.
> My patch make the responded bytes as expected and the interrupt will not
> happen.
What makes you think padding the response with zeros is the right thing to do?
I think this is a bug elsewhere (maybe in your device driver).
Paul
next prev parent reply other threads:[~2007-04-22 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 2:01 [Qemu-devel] scsi interface patch Wang Cheng Yeh
2007-04-22 9:54 ` Hetz Ben Hamo
[not found] ` <a20f395e0704220615n268ca374y152fb23ad225ade7@mail.gmail.com>
2007-04-22 13:22 ` Wang Cheng Yeh
2007-04-22 13:54 ` Paul Brook [this message]
2007-04-22 15:26 ` Wang Cheng Yeh
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=200704221454.27190.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=cywang.eda@gmail.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).