From: Anthony Liguori <anthony@codemonkey.ws>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 03/20] sb16: remove IO_READ_PROTO
Date: Thu, 22 Oct 2009 15:41:14 -0500 [thread overview]
Message-ID: <4AE0C36A.1090608@codemonkey.ws> (raw)
In-Reply-To: <Pine.LNX.4.64.0910230032240.2584@linmac.oyster.ru>
malc wrote:
> On Thu, 22 Oct 2009, Juan Quintela wrote:
>
> No.
>
I was going to say, "Because..."
But seeing as the commit message was completely empty, "No." is a pretty
reasonable response.
Juan, can you explain the justification for removing this a bit more?
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-10-22 20:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 14:36 [Qemu-devel] [PATCH 00/20] Port audio to vmstate Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 01/20] audio: fix compilation of DEBUG_PLIVE Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 02/20] audio: port to vmstate Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 03/20] sb16: remove IO_READ_PROTO Juan Quintela
2009-10-22 20:32 ` malc
2009-10-22 20:41 ` Anthony Liguori [this message]
2009-10-22 14:36 ` [Qemu-devel] [PATCH 04/20] sb16: remove IO_WRITE_PROTO Juan Quintela
2009-10-22 20:32 ` malc
2009-10-22 14:36 ` [Qemu-devel] [PATCH 05/20] sb16: port to vmstate Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 06/20] es1370: remove IO_READ_PROTO Juan Quintela
2009-10-22 20:33 ` malc
2009-10-22 14:36 ` [Qemu-devel] [PATCH 07/20] es1370: remove IO_WRITE_PROTO Juan Quintela
2009-10-22 20:33 ` malc
2009-10-22 14:36 ` [Qemu-devel] [PATCH 08/20] es1370: port to vmstate Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 09/20] adlib: remove IO_READ_PROTO Juan Quintela
2009-10-22 20:34 ` malc
2009-10-22 14:36 ` [Qemu-devel] [PATCH 10/20] adlib: remove IO_WRITE_PROTO Juan Quintela
2009-10-22 20:34 ` malc
2009-10-22 14:36 ` [Qemu-devel] [PATCH 11/20] c4231a: remove IO_READ_PROTO Juan Quintela
2009-10-22 20:34 ` malc
2009-10-22 14:36 ` [Qemu-devel] [PATCH 12/20] c4231a: remove IO_WRITE_PROTO Juan Quintela
2009-10-22 20:35 ` malc
2009-10-22 14:36 ` [Qemu-devel] [PATCH 13/20] c4231a: port to vmstate Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 14/20] gus: remove IO_READ_PROTO Juan Quintela
2009-10-22 20:35 ` malc
2009-10-22 14:36 ` [Qemu-devel] [PATCH 15/20] gus: remove IO_WRITE_PROTO Juan Quintela
2009-10-22 20:35 ` malc
2009-10-22 14:36 ` [Qemu-devel] [PATCH 16/20] gus: port to vmstate Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 17/20] ac97: sizeof returns unsigned long Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 18/20] ac97: recalculate active after loadvm Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 19/20] ac97: up savevm version and remove active from state Juan Quintela
2009-10-22 14:36 ` [Qemu-devel] [PATCH 20/20] ac97: port to vmstate Juan Quintela
2009-10-22 20:44 ` [Qemu-devel] [PATCH 00/20] Port audio " malc
2009-10-23 12:26 ` [Qemu-devel] " Juan Quintela
2009-10-23 12:41 ` malc
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=4AE0C36A.1090608@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=av1474@comtv.ru \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).