From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 00/15] SCSI changes for 2014-05-20
Date: Tue, 20 May 2014 20:14:38 +0200 [thread overview]
Message-ID: <1400609682-22166-1-git-send-email-pbonzini@redhat.com> (raw)
Peter,
The following changes since commit 6a86dec61921163b6ab582df988416a6f0ca0ed5:
[PATCH] block/iscsi: bump year in copyright notice (2014-05-05 10:04:30 +0200)
are available in the git repository at:
git://github.com/bonzini/qemu.git scsi-next
for you to fetch changes up to 5a7733b0b728bb4900bdeed12fef22651ce0ab58:
megasas: remove buildtime strings (2014-05-20 16:14:29 +0200)
Yesterday's pull request had a problem with old libiscsi, so I am sending
another one. Sorry for the inconvenience.
----------------------------------------------------------------
Jeff Cody (1):
block: iscsi build fix if LIBISCSI_FEATURE_IOVECTOR is not defined
Markus Armbruster (2):
scsi: Document intentional fall through in scsi_req_length()
virtio-scsi: Plug memory leak on virtio_scsi_push_event() error path
Olaf Hering (1):
megasas: remove buildtime strings
block/iscsi.c | 4 +---
hw/scsi/megasas.c | 4 ++--
hw/scsi/scsi-bus.c | 2 ++
hw/scsi/virtio-scsi.c | 3 ++-
4 files changed, 7 insertions(+), 6 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-05-20 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 18:14 Paolo Bonzini [this message]
2014-05-20 18:14 ` [Qemu-devel] [PULL 1/4] scsi: Document intentional fall through in scsi_req_length() Paolo Bonzini
2014-05-20 18:14 ` [Qemu-devel] [PULL 2/4] virtio-scsi: Plug memory leak on virtio_scsi_push_event() error path Paolo Bonzini
2014-05-20 18:14 ` [Qemu-devel] [PULL 3/4] block: iscsi build fix if LIBISCSI_FEATURE_IOVECTOR is not defined Paolo Bonzini
2014-05-20 18:14 ` [Qemu-devel] [PULL 4/4] megasas: remove buildtime strings Paolo Bonzini
2014-05-22 15:13 ` [Qemu-devel] [PULL 00/15] SCSI changes for 2014-05-20 Peter Maydell
2014-05-22 15:20 ` 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=1400609682-22166-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@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 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).