From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, Eric Farman <farman@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/3] scsi-generic and BLKSECTGET
Date: Tue, 24 Jan 2017 12:23:16 +0100 [thread overview]
Message-ID: <ff2fd02a-09ea-a28f-eb6e-e1858efff552@redhat.com> (raw)
In-Reply-To: <20170122142959.GA12419@lemon.Home>
On 22/01/2017 15:29, Fam Zheng wrote:
> On Fri, 01/20 17:25, Eric Farman wrote:
>> Changes:
>> v2->v3:
>> - Move byte/sector conversions to patch 2 [Fam Zheng]
>> - Rename "max_sectors" when holding a byte value [Fam Zheng]
>> v1->v2:
>> - Patch 3, make hdev_get_max_transfer_length return bytes [Fam Zheng]
>
> Reviewed-by: Fam Zheng <famz@redhat.com>
Looks good, who's merging this? :)
Paolo
next prev parent reply other threads:[~2017-01-24 11:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 16:25 [Qemu-devel] [PATCH v3 0/3] scsi-generic and BLKSECTGET Eric Farman
2017-01-20 16:25 ` [Qemu-devel] [PATCH v3 1/3] hw/scsi: Fix debug message of cdb structure in scsi-generic Eric Farman
2017-01-20 16:25 ` [Qemu-devel] [PATCH v3 2/3] block: Fix target variable of BLKSECTGET ioctl Eric Farman
2017-02-01 0:25 ` [Qemu-devel] [Qemu-block] " Max Reitz
2017-02-01 13:18 ` Eric Farman
2017-01-20 16:25 ` [Qemu-devel] [PATCH v3 3/3] block: get max_transfer limit for char (scsi-generic) devices Eric Farman
2017-01-22 14:29 ` [Qemu-devel] [PATCH v3 0/3] scsi-generic and BLKSECTGET Fam Zheng
2017-01-24 11:23 ` Paolo Bonzini [this message]
2017-01-24 12:09 ` Fam Zheng
2017-01-24 12:17 ` Eric Farman
2017-01-31 11:37 ` [Qemu-devel] [Qemu-block] " John Snow
2017-01-31 23:47 ` Max Reitz
2017-02-01 9:51 ` John Snow
2017-02-01 19:55 ` Max Reitz
2017-02-08 22:33 ` Max Reitz
2017-02-09 9:32 ` [Qemu-devel] " 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=ff2fd02a-09ea-a28f-eb6e-e1858efff552@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=farman@linux.vnet.ibm.com \
--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).