All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Yuan <namei.unix@gmail.com>
To: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: kwolf@redhat.com, pbonzini@redhat.com, sheepdog@lists.wpkg.org,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [sheepdog] [PATCH v2 0/9] sheepdog: reconnect server after connection failure
Date: Thu, 25 Jul 2013 14:02:38 +0800	[thread overview]
Message-ID: <20130725060238.GC24069@ubuntu-precise> (raw)
In-Reply-To: <87fvv3gp6y.wl%morita.kazutaka@lab.ntt.co.jp>

On Thu, Jul 25, 2013 at 02:53:57PM +0900, MORITA Kazutaka wrote:
> At Thu, 25 Jul 2013 13:25:33 +0800,
> Liu Yuan wrote:
> > 
> > Hello Kazutaka,
> > 
> >    I have two patches fixing the problems I found on my testing and they are
> > complementary patches. Please consider sending them on top of your patch set.
> 
> Thanks a lot for your comments and patches, but I've already prepared
> patches, which would be probably better fixes.  I'll send the v3
> series soon.  It'd be appreciated if you would give a review for it.
> 

Okay, no problem. Well, in my previous patches, patch 2/2 isn't correct, I did a
wrong manual rebase by hasty copy. Just FYI.

Thanks
Yuan

      reply	other threads:[~2013-07-25  6:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  7:56 [Qemu-devel] [PATCH v2 0/9] sheepdog: reconnect server after connection failure MORITA Kazutaka
2013-07-24  7:56 ` [Qemu-devel] [PATCH v2 1/9] ignore SIGPIPE in qemu-img and qemu-io MORITA Kazutaka
2013-07-24  7:56 ` [Qemu-devel] [PATCH v2 2/9] iov: handle EOF in iov_send_recv MORITA Kazutaka
2013-07-24  7:56 ` [Qemu-devel] [PATCH v2 3/9] sheepdog: check return values of qemu_co_recv/send correctly MORITA Kazutaka
2013-07-24  7:56 ` [Qemu-devel] [PATCH v2 4/9] sheepdog: handle vdi objects in resend_aio_req MORITA Kazutaka
2013-07-24  7:56 ` [Qemu-devel] [PATCH v2 5/9] sheepdog: reload inode outside of resend_aioreq MORITA Kazutaka
2013-07-24  7:56 ` [Qemu-devel] [PATCH v2 6/9] coroutine: add co_aio_sleep_ns() to allow sleep in block drivers MORITA Kazutaka
2013-07-24  7:56 ` [Qemu-devel] [PATCH v2 7/9] sheepdog: try to reconnect to sheepdog after network error MORITA Kazutaka
2013-07-24  7:56 ` [Qemu-devel] [PATCH v2 8/9] sheepdog: make add_aio_request and send_aioreq void functions MORITA Kazutaka
2013-07-24  7:56 ` [Qemu-devel] [PATCH v2 9/9] sheepdog: cancel aio requests if possible MORITA Kazutaka
2013-07-24  8:28 ` [Qemu-devel] [sheepdog] [PATCH v2 0/9] sheepdog: reconnect server after connection failure Liu Yuan
2013-07-24  9:07   ` MORITA Kazutaka
2013-07-24 15:42     ` Liu Yuan
2013-07-25  3:36       ` Liu Yuan
2013-07-25  5:25         ` [Qemu-devel] " Liu Yuan
2013-07-25  5:25           ` [Qemu-devel] [PATCH 1/2] sheepdog: correct signedness of comparison Liu Yuan
2013-07-25  5:25           ` [Qemu-devel] [PATCH 2/2] sheepdog: put aio request into failed list when failing to send request Liu Yuan
2013-07-25  5:53           ` [Qemu-devel] [sheepdog] [PATCH v2 0/9] sheepdog: reconnect server after connection failure MORITA Kazutaka
2013-07-25  6:02             ` Liu Yuan [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=20130725060238.GC24069@ubuntu-precise \
    --to=namei.unix@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=morita.kazutaka@lab.ntt.co.jp \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sheepdog@lists.wpkg.org \
    --cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.