qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: qemu-block@nongnu.org
Cc: peter.maydell@linaro.org, jcody@redhat.com,
	qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: [Qemu-devel] [PULL 0/2] Block patches
Date: Tue,  5 Jun 2018 10:19:31 -0400	[thread overview]
Message-ID: <20180605141933.30169-1-jcody@redhat.com> (raw)

The following changes since commit 41feb5b955f0d7c9d071b2c5adbc404ae2895c7a:

  Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-3.0-pull-request' into staging (2018-06-05 10:38:33 +0100)

are available in the git repository at:

  git://github.com/codyprime/qemu-kvm-jtc.git tags/block-pull-request

for you to fetch changes up to 68acc99f143b60ec4faa2903065b187d4d3c4bf3:

  sheepdog: remove huge BSS object (2018-06-05 10:15:12 -0400)

----------------------------------------------------------------
Sheepdog patches
----------------------------------------------------------------

Paolo Bonzini (2):
  sheepdog: cleanup repeated expression
  sheepdog: remove huge BSS object

 block/sheepdog.c | 28 +++++++++++++++-------------
 1 file changed, 15 insertions(+), 13 deletions(-)

-- 
2.13.6

             reply	other threads:[~2018-06-05 14:19 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 14:19 Jeff Cody [this message]
2018-06-05 14:19 ` [Qemu-devel] [PULL 1/2] sheepdog: cleanup repeated expression Jeff Cody
2018-06-05 14:19 ` [Qemu-devel] [PULL 2/2] sheepdog: remove huge BSS object Jeff Cody
2018-06-05 15:11 ` [Qemu-devel] [PULL 0/2] Block patches Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2019-08-22 15:53 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-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-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=20180605141933.30169-1-jcody@redhat.com \
    --to=jcody@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --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 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).