qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Frediano Ziglio <freddy77@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	devin122@gmail.com, Stefan Hajnoczi <stefanha@gmail.com>,
	Jagane Sundar <jagane@sundar.org>, Dor Laor <dlaor@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>,
	Feiran Zheng <famcool@gmail.com>,
	Jes Sorensen <Jes.Sorensen@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] Block layer roadmap
Date: Thu, 28 Jul 2011 14:16:37 +0200	[thread overview]
Message-ID: <20110728121637.GA17234@lst.de> (raw)
In-Reply-To: <CAHt6W4cs-ULyqJAK0S=uEcazvZB0_9+KwtRS8MWX1Pj1iRSDKQ@mail.gmail.com>

On Thu, Jul 28, 2011 at 02:15:38PM +0200, Frediano Ziglio wrote:
> 
> This has nothing (or few) to do with threads. Instead of splitting
> functions in callbacks at every synchronous function it allow to write
> more readable code.

Thanks for repeating my statement that it doesn't fix the real thing
but just adds syntactic sugar.  

  reply	other threads:[~2011-07-28 12:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 12:37 [Qemu-devel] Block layer roadmap Stefan Hajnoczi
2011-07-27 12:50 ` Anthony Liguori
2011-07-28 10:05 ` Kevin Wolf
2011-07-28 12:08   ` Christoph Hellwig
2011-07-28 12:29     ` Kevin Wolf
2011-07-28 10:52 ` Stefan Hajnoczi
2011-07-28 12:09 ` Christoph Hellwig
2011-07-28 12:15   ` Frediano Ziglio
2011-07-28 12:16     ` Christoph Hellwig [this message]
2011-07-28 12:35   ` Kevin Wolf
2011-07-28 12:54     ` Stefan Hajnoczi
2011-07-28 13:10       ` Kevin Wolf
2011-07-28 13:11         ` Stefan Hajnoczi
2011-07-28 12:52   ` Anthony Liguori
2011-07-29 12:35 ` Stefan Hajnoczi

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=20110728121637.GA17234@lst.de \
    --to=hch@lst.de \
    --cc=Jes.Sorensen@redhat.com \
    --cc=armbru@redhat.com \
    --cc=devin122@gmail.com \
    --cc=dlaor@redhat.com \
    --cc=famcool@gmail.com \
    --cc=freddy77@gmail.com \
    --cc=jagane@sundar.org \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).