From: Peter Maydell <peter.maydell@linaro.org>
To: Keith Busch <kbusch@kernel.org>
Cc: Klaus Jensen <its@irrelevant.dk>,
Klaus Jensen <k.jensen@samsung.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PULL] nvme emulation patches for 5.2
Date: Mon, 2 Nov 2020 20:29:32 +0000 [thread overview]
Message-ID: <CAFEAcA-0MM1QWMMQomp99HddpTev23M8iyv=yUqYZYbPDyBa1g@mail.gmail.com> (raw)
In-Reply-To: <20201102152747.GA28552@redsun51.ssa.fujisawa.hgst.com>
On Mon, 2 Nov 2020 at 15:27, Keith Busch <kbusch@kernel.org> wrote:
>
> Hi Peter,
>
> We are sorting out Klaus' signature authentication this week, but in the
> interest of timing, I've signed our pull request for this round.
>
> The following changes since commit 1dc887329a10903940501b43e8c0cc67af7c06d5:
>
> Merge remote-tracking branch 'remotes/philmd-gitlab/tags/sd-next-20201026' into staging (2020-10-26 17:19:26 +0000)
>
> are available in the Git repository at:
>
> git://git.infradead.org/qemu-nvme.git tags/pull-nvme-20201102
>
> for you to fetch changes up to 843c8f91a7ad63f8f3e4e564d3f41f3d030ab8a9:
>
> hw/block/nvme: fix queue identifer validation (2020-10-27 11:29:25 +0100)
>
> nvme emulation patches for 5.2
>
> - lots of cleanups
> - add support for scatter/gather lists
> - add support for multiple namespaces (adds new nvme-ns device)
> - change default pci vendor/device id
> - add support for per-namespace smart log
>
> ----------------------------------------------------------------
> nvme pull 2 Nov 2020
>
> ----------------------------------------------------------------
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/5.2
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2020-11-02 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 15:27 [PULL] nvme emulation patches for 5.2 Keith Busch
2020-11-02 15:43 ` Philippe Mathieu-Daudé
2020-11-02 20:29 ` Peter Maydell [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='CAFEAcA-0MM1QWMMQomp99HddpTev23M8iyv=yUqYZYbPDyBa1g@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.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 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).