From: Paolo Bonzini <pbonzini@redhat.com>
To: Ronnie Sahlberg <ronniesahlberg@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/1] ISCSI: Optimize how we set up the events
Date: Fri, 25 May 2012 13:12:35 +0200 [thread overview]
Message-ID: <4FBF6923.7080302@redhat.com> (raw)
In-Reply-To: <1337941512-10091-1-git-send-email-ronniesahlberg@gmail.com>
Il 25/05/2012 12:25, Ronnie Sahlberg ha scritto:
> This patch updates how iscsi sets up the read and write events so
> that we only call qemu_aio_set_fd_handler() and qemu_notify_event()
> when we actually need to.
Applied, thanks.
Paolo
prev parent reply other threads:[~2012-05-25 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 10:25 [Qemu-devel] [PATCH 0/1] ISCSI: Optimize how we set up the events Ronnie Sahlberg
2012-05-25 10:25 ` [Qemu-devel] [PATCH] ISCSI: redo how we set up the events to only call qemu_aio_set_fd_handler() and qemu_notify_event() if something has changed Ronnie Sahlberg
2012-05-25 11:12 ` Paolo Bonzini [this message]
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=4FBF6923.7080302@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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).