From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/2] Block layer patches
Date: Fri, 12 Jul 2019 15:52:51 +0200 [thread overview]
Message-ID: <20190712135253.9410-1-kwolf@redhat.com> (raw)
The following changes since commit a2a9d4adabe340617a24eb73a8b2a116d28a6b38:
Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-4.1-20190712' into staging (2019-07-12 11:06:48 +0100)
are available in the Git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch changes up to 867eccfed84f96b54f4a432c510a02c2ce03b430:
file-posix: Use max transfer length/segment count only for SCSI passthrough (2019-07-12 15:42:23 +0200)
----------------------------------------------------------------
Block layer patches:
- file-posix: Fix max transfer length for non-SCSI-passthrough
- iotests: Fix 082 reference output
----------------------------------------------------------------
Eric Blake (1):
iotests: Update 082 expected output
Maxim Levitsky (1):
file-posix: Use max transfer length/segment count only for SCSI passthrough
block/file-posix.c | 54 ++++++++++++++++++++++++----------------------
tests/qemu-iotests/082.out | 54 +++++++++++++++++++++++-----------------------
2 files changed, 55 insertions(+), 53 deletions(-)
next reply other threads:[~2019-07-12 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 13:52 Kevin Wolf [this message]
2019-07-12 13:52 ` [Qemu-devel] [PULL 1/2] iotests: Update 082 expected output Kevin Wolf
2019-07-12 13:52 ` [Qemu-devel] [PULL 2/2] file-posix: Use max transfer length/segment count only for SCSI passthrough Kevin Wolf
2019-07-12 15:32 ` [Qemu-devel] [PULL 0/2] Block layer patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2019-04-08 16:34 Kevin Wolf
2019-04-08 19:10 ` Peter Maydell
2019-04-08 19:10 ` Peter Maydell
2018-12-03 16:58 Kevin Wolf
2018-12-03 17:43 ` Peter Maydell
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=20190712135253.9410-1-kwolf@redhat.com \
--to=kwolf@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 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.