From: Max Reitz <mreitz@redhat.com>
To: Li Qiang <liq3ea@163.com>,
keith.busch@intel.com, kwolf@redhat.com, philmd@redhat.com
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] nvme small fix
Date: Mon, 21 Jan 2019 01:10:18 +0100 [thread overview]
Message-ID: <858c1f7f-d48e-a946-309d-1a7afdaf4aca@redhat.com> (raw)
In-Reply-To: <20190120055558.32984-1-liq3ea@163.com>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On 20.01.19 06:55, Li Qiang wrote:
> This patchset contains small fix.
>
> Change since v2:
> For patch 2:
> 1. add nvme command
> 2. check num_queues first
>
> Change since v1:
>
> 1. drop the patch of checking return value of msix_init_exclusive_bar
> 2. return when nvme's num_queues configuration is 0
>
> Li Qiang (3):
> nvme: use TYPE_NVME instead of constant string
> nvme: ensure the num_queues is not zero
> nvme: use pci_dev directly in nvme_realize
>
> hw/block/nvme.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
Thanks, applied to my block branch:
https://git.xanclic.moe/XanClic/qemu/commits/branch/block
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-01-21 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 5:55 [Qemu-devel] [PATCH 0/3] nvme small fix Li Qiang
2019-01-20 5:55 ` [Qemu-devel] [PATCH 1/3] nvme: use TYPE_NVME instead of constant string Li Qiang
2019-01-20 5:55 ` [Qemu-devel] [PATCH 2/3] nvme: ensure the num_queues is not zero Li Qiang
2019-01-20 5:55 ` [Qemu-devel] [PATCH 3/3] nvme: use pci_dev directly in nvme_realize Li Qiang
2019-01-21 0:10 ` Max Reitz [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=858c1f7f-d48e-a946-309d-1a7afdaf4aca@redhat.com \
--to=mreitz@redhat.com \
--cc=keith.busch@intel.com \
--cc=kwolf@redhat.com \
--cc=liq3ea@163.com \
--cc=philmd@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).