[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: [PATCH] tapdisk cleanup

To: "Jun Koi" <junkoi2004@xxxxxxxxx>
From: "Andrew Warfield" <andrew.warfield@xxxxxxxxxxxx>
Date: Fri, 1 Sep 2006 13:23:21 -0700
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>, jac90@xxxxxxxxx
Delivery-date: Fri, 01 Sep 2006 13:23:47 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Lu3PHBXRW3AkaFkAmq3PqQlSMm7mVk2GrUHLV+oWJwf06eh/FB25nw1rk0hGey3/Dy8wX0J0quAk7trtQQkDZH8CS1kTo2r3ataadO6ayFHFJTEbO3UH7rRE7Ucu3D+l6fY3KbXXd4G7D7Kz0fitpoIy2ASQ4YN39l5iWzHWukk=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Applied.  Thanks Jun.  If you wanted to go through and clean up the
rest of the io_fd uses, i.e. to address them all as READ/WRITE rather
than in loops to 2, that would be appreciated.  The current structure
of thos io_fds may be a little over-extensible at the moment ;)

a.

On 9/1/06, Jun Koi <junkoi2004@xxxxxxxxx> wrote:

Hi Julian and Andrew,

This patch cleans tapdisk, please apply.

Sign-off-by: Jun Koi <junkoi2004@xxxxxxxxx>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Follow-Ups:
- Re: [Xen-devel] Re: [PATCH] tapdisk cleanup
  - From: NAHieu

References:
- [Xen-devel] [PATCH] tapdisk cleanup
  - From: Jun Koi

Prev by Date: Re: [Xen-devel] [Xense-devel][RFC][PATCH][1/4] Xen Security Modules: XSM
Next by Date: [Xen-devel] Re: [PATCH] block_sync bugfix & cleanup
Previous by thread: [Xen-devel] [PATCH] tapdisk cleanup
Next by thread: Re: [Xen-devel] Re: [PATCH] tapdisk cleanup
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.