All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Fam Zheng <famz@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/2] Block patches
Date: Fri, 30 Jun 2017 17:55:52 +0100	[thread overview]
Message-ID: <CAFEAcA-Bexxq2S0EWxmKD4wJ3HBnCsjgFxEqYgd+FuEA6opALQ@mail.gmail.com> (raw)
In-Reply-To: <20170630141040.15353-1-famz@redhat.com>

On 30 June 2017 at 15:10, Fam Zheng <famz@redhat.com> wrote:
> The following changes since commit 36f87b4513373b3cd79c87c9197d17face95d4ac:
>
>   Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-2.10-20170630' into staging (2017-06-30 11:58:49 +0100)
>
> are available in the git repository at:
>
>   git://github.com/famz/qemu.git tags/block-pull-request
>
> for you to fetch changes up to c61e684e44272f2acb2bef34cf2aa234582a73a9:
>
>   block: Exploit BDRV_BLOCK_EOF for larger zero blocks (2017-06-30 21:48:06 +0800)
>
> ----------------------------------------------------------------
>
> Hi Peter,
>
> Here are Eric Blake's enhancement to block layer API. Thanks!
>
> ----------------------------------------------------------------

Applied, thanks.

-- PMM

  parent reply	other threads:[~2017-06-30 16:56 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30 14:10 [Qemu-devel] [PULL 0/2] Block patches Fam Zheng
2017-06-30 14:10 ` [Qemu-devel] [PULL 1/2] block: Add BDRV_BLOCK_EOF to bdrv_get_block_status() Fam Zheng
2017-06-30 14:10 ` [Qemu-devel] [PULL 2/2] block: Exploit BDRV_BLOCK_EOF for larger zero blocks Fam Zheng
2017-06-30 16:55 ` Peter Maydell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-22 15:53 [Qemu-devel] [PULL 0/2] Block patches Stefan Hajnoczi
2019-08-27  9:00 ` Peter Maydell
2019-01-14 16:34 Stefan Hajnoczi
2019-01-15 18:07 ` Peter Maydell
2018-12-12  9:52 Stefan Hajnoczi
2018-12-13 13:05 ` Peter Maydell
2018-10-29 13:56 Stefan Hajnoczi
2018-10-29 18:23 ` Peter Maydell
2018-10-12  1:50 Fam Zheng
2018-10-12 11:39 ` Peter Maydell
2018-08-22  3:43 Jeff Cody
2018-08-23 18:02 ` Peter Maydell
2018-06-27 14:48 Stefan Hajnoczi
2018-06-28 16:43 ` Peter Maydell
2018-07-01 14:58 ` no-reply
2018-07-02  6:19   ` Fam Zheng
2018-06-05 14:19 Jeff Cody
2018-06-05 15:11 ` Peter Maydell
2018-02-01  4:06 Jeff Cody
2018-02-02 10:57 ` Peter Maydell
2018-01-22 12:40 Stefan Hajnoczi
2018-01-22 13:54 ` Stefan Hajnoczi
2017-07-18  4:17 Jeff Cody
2017-07-18 20:13 ` Peter Maydell
2017-07-17 15:40 Stefan Hajnoczi
2017-07-18 13:13 ` Peter Maydell
2017-06-28 12:20 Stefan Hajnoczi
2017-06-28 12:48 ` Stefan Hajnoczi
2017-06-14 21:55 Jeff Cody
2017-06-14 22:26 ` no-reply
2017-06-15  4:30   ` Jeff Cody
2017-06-15  7:28     ` Juan Quintela
2017-06-20 10:13 ` Peter Maydell
2017-02-28  4:37 Jeff Cody
2017-02-28 14:49 ` Peter Maydell
2016-09-13  5:42 Jeff Cody
2016-09-13 11:59 ` Peter Maydell
2016-03-17 11:08 Stefan Hajnoczi
2016-03-17 12:43 ` Peter Maydell
2015-09-02 16:01 Stefan Hajnoczi
2015-09-03 10:14 ` Peter Maydell
2015-08-14 14:41 Stefan Hajnoczi
2015-08-14 15:52 ` Peter Maydell
2015-03-12 19:10 Stefan Hajnoczi
2015-03-13 11:00 ` Peter Maydell
2013-03-25 11:00 Stefan Hajnoczi
2013-03-25 11:54 ` Richard W.M. Jones
2013-03-25 12:15 ` Eric Blake

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=CAFEAcA-Bexxq2S0EWxmKD4wJ3HBnCsjgFxEqYgd+FuEA6opALQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=famz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.