All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/2] Block patches
Date: Fri, 14 Aug 2015 16:52:07 +0100	[thread overview]
Message-ID: <CAFEAcA8+KY-RRxoMNDFBtvoTCq+b7UUhNeUOCDf1bbSFmE7Wvw@mail.gmail.com> (raw)
In-Reply-To: <1439563278-11873-1-git-send-email-stefanha@redhat.com>

On 14 August 2015 at 15:41, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> The following changes since commit 2be4f242b50a84bf360df02480b173bfed161107:
>
>   Merge remote-tracking branch 'remotes/ehabkost/tags/x86-pull-request' into staging (2015-08-04 16:51:24 +0100)
>
> are available in the git repository at:
>
>   git://github.com/stefanha/qemu.git tags/block-pull-request
>
> for you to fetch changes up to 92e11a17612108b1729bde4ce61aad0cc1ce5889:
>
>   throttle: add throttle_max_is_missing_limit() test (2015-08-05 12:53:48 +0100)
>
> ----------------------------------------------------------------
>
> ----------------------------------------------------------------

Applied, thanks.

-- PMM

  parent reply	other threads:[~2015-08-14 15:52 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 14:41 [Qemu-devel] [PULL 0/2] Block patches Stefan Hajnoczi
2015-08-14 14:41 ` [Qemu-devel] [PULL 1/2] throttle: refuse bps_max/iops_max without bps/iops Stefan Hajnoczi
2015-08-14 14:41 ` [Qemu-devel] [PULL 2/2] throttle: add throttle_max_is_missing_limit() test Stefan Hajnoczi
2015-08-14 15:52 ` 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-30 14:10 Fam Zheng
2017-06-30 16:55 ` 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-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=CAFEAcA8+KY-RRxoMNDFBtvoTCq+b7UUhNeUOCDf1bbSFmE7Wvw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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.