All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charlie Shepherd <charlie@ctshepherd.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, stefanha@gmail.com, gabriel@kerneis.info,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Make cow_co_is_allocated and cow_update_bitmap more efficient
Date: Tue, 20 Aug 2013 14:50:22 +0100	[thread overview]
Message-ID: <5213741E.3040702@ctshepherd.com> (raw)
In-Reply-To: <521372F7.2090508@redhat.com>

On 20/08/2013 14:45, Paolo Bonzini wrote:
> I had very similar patches in my series to add get_block_status...

Ah, sorry if I've duplicated something you've already done. Stefan 
encouraged me to contribute to an area of QEMU I found interesting and 
seeing the XXX I thought I'd take a shot at improving the code. Where 
should I look in the future for patches like this?


Charlie

  reply	other threads:[~2013-08-20 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 13:42 [Qemu-devel] [PATCH] Make cow_co_is_allocated and cow_update_bitmap more efficient Charlie Shepherd
2013-08-20 13:45 ` Paolo Bonzini
2013-08-20 13:50   ` Charlie Shepherd [this message]
2013-08-20 14:03     ` Paolo Bonzini

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=5213741E.3040702@ctshepherd.com \
    --to=charlie@ctshepherd.com \
    --cc=gabriel@kerneis.info \
    --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 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.