From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Xen patches - status summary
Date: Wed, 03 Sep 2008 21:53:50 -0500 [thread overview]
Message-ID: <48BF4DBE.6040206@codemonkey.ws> (raw)
In-Reply-To: <18621.28008.90183.80897@mariner.uk.xensource.com>
Ian Jackson wrote
> [3] Re: IDE error checking
>
> I summarised the discussion in my message `[REPOST] [PATCH 0/2]'.
> There has been no recent response. For the reasons I explain, I think
> this patch should be applied now without waiting for any
> ENOSPC-auto-pause feature.
For the vast majority of users, ENOSPC is the only realistic error that
will occur. I don't think a patch that doesn't handle ENOSPC in a sane
way is really that useful.
> [4] Re: IDE write cache
>
I have to review these patches but I do agree with the theory behind them.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-09-04 2:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 16:44 [Qemu-devel] Xen patches - status summary Ian Jackson
2008-09-03 18:43 ` Gerd Hoffmann
2008-09-04 2:47 ` Anthony Liguori
2008-09-05 10:33 ` Ian Jackson
2008-09-06 22:00 ` Anthony Liguori
2008-09-07 3:16 ` Anthony Liguori
2008-09-04 2:53 ` Anthony Liguori [this message]
2008-09-05 10:23 ` Ian Jackson
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=48BF4DBE.6040206@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).