From: Maxim Levitsky <mlevitsk@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, Kevin Wolf <kwolf@redhat.com>,
John Snow <jsnow@redhat.com>,
qemu-block@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/3] Few bugfixes for userspace nvme driver
Date: Sun, 21 Jul 2019 11:36:55 +0300 [thread overview]
Message-ID: <07d47f44f792c7710e699a82ec5abb0d91f7ac30.camel@redhat.com> (raw)
In-Reply-To: <e410dc4e-0d43-dc89-4935-fba9ce164cdf@redhat.com>
On Fri, 2019-07-19 at 11:51 +0200, Max Reitz wrote:
> On 16.07.19 18:30, Maxim Levitsky wrote:
> > This is reduced version of patch series for userspace nvme driver,
> > that only includes the bugfixes I made.
> >
> > Best regards,
> > Maxim Levitsky
> >
> > Maxim Levitsky (3):
> > block/nvme: fix doorbell stride
> > block/nvme: support larger that 512 bytes sector devices
> > block/nvme: don't touch the completion entries
> >
> > block/nvme.c | 52 ++++++++++++++++++++++++++++++++++++++++++----------
> > 1 file changed, 42 insertions(+), 10 deletions(-)
>
> Thanks, applied to my block branch:
>
> https://git.xanclic.moe/XanClic/qemu/commits/branch/block
>
> Max
>
Thank you!!
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2019-07-21 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 16:30 [Qemu-devel] [PATCH v4 0/3] Few bugfixes for userspace nvme driver Maxim Levitsky
2019-07-16 16:30 ` [Qemu-devel] [PATCH v4 1/3] block/nvme: fix doorbell stride Maxim Levitsky
2019-07-16 16:30 ` [Qemu-devel] [PATCH v4 2/3] block/nvme: support larger that 512 bytes sector devices Maxim Levitsky
2019-07-16 16:30 ` [Qemu-devel] [PATCH v4 3/3] block/nvme: don't touch the completion entries Maxim Levitsky
2019-07-19 9:51 ` [Qemu-devel] [PATCH v4 0/3] Few bugfixes for userspace nvme driver Max Reitz
2019-07-21 8:36 ` Maxim Levitsky [this message]
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=07d47f44f792c7710e699a82ec5abb0d91f7ac30.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.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).