From: Klaus Jensen <its@irrelevant.dk>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Keith Busch <kbusch@kernel.org>,
Klaus Jensen <k.jensen@samsung.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PULL 00/30] nvme emulation patches for 5.2
Date: Thu, 29 Oct 2020 12:52:54 +0100 [thread overview]
Message-ID: <20201029115254.GA777050@apples.localdomain> (raw)
In-Reply-To: <CAFEAcA8EcEfaFZYUicbL5ShA5y5sTP7hmNNX5Ot=3ZyAGnV81A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
On Oct 29 11:39, Peter Maydell wrote:
> On Tue, 27 Oct 2020 at 10:49, Klaus Jensen <its@irrelevant.dk> wrote:
> >
> > From: Klaus Jensen <k.jensen@samsung.com>
> >
> > Hi Peter,
> >
> > 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/nvme-next-pull-request
> >
> > 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
>
> Hi. This tag appears to have been signed with a GPG key
> which isn't one that's been used before for an nvme pullreq
> and which isn't on the public GPG servers...
>
Uhm. Keith, can we coordinate a keysigning?
Would a signature by Keith on my key be acceptable to you Peter? That
way Keith doesn't have to create a new tag and bomb the list again.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-29 11:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 10:49 [PULL 00/30] nvme emulation patches for 5.2 Klaus Jensen
2020-10-27 10:49 ` [PULL 01/30] hw/block/nvme: fix typo in trace event Klaus Jensen
2020-10-27 10:49 ` [PULL 02/30] pci: pass along the return value of dma_memory_rw Klaus Jensen
2020-10-27 11:10 ` Klaus Jensen
2020-10-27 10:49 ` [PULL 03/30] hw/block/nvme: handle dma errors Klaus Jensen
2020-10-27 10:49 ` [PULL 04/30] hw/block/nvme: commonize nvme_rw error handling Klaus Jensen
2020-10-27 10:49 ` [PULL 05/30] hw/block/nvme: alignment style fixes Klaus Jensen
2020-10-27 10:49 ` [PULL 06/30] hw/block/nvme: add a lba to bytes helper Klaus Jensen
2020-10-27 10:49 ` [PULL 07/30] hw/block/nvme: fix endian conversion Klaus Jensen
2020-10-27 10:49 ` [PULL 08/30] hw/block/nvme: add symbolic command name to trace events Klaus Jensen
2020-10-27 10:49 ` [PULL 09/30] hw/block/nvme: refactor aio submission Klaus Jensen
2020-10-27 10:49 ` [PULL 10/30] hw/block/nvme: default request status to success Klaus Jensen
2020-10-27 10:49 ` [PULL 11/30] hw/block/nvme: harden cmb access Klaus Jensen
2020-10-27 10:49 ` [PULL 12/30] hw/block/nvme: add support for scatter gather lists Klaus Jensen
2020-11-04 9:44 ` Max Reitz
2020-10-27 10:49 ` [PULL 13/30] hw/block/nvme: add support for sgl bit bucket descriptor Klaus Jensen
2020-10-27 10:49 ` [PULL 14/30] hw/block/nvme: refactor identify active namespace id list Klaus Jensen
2020-10-27 10:49 ` [PULL 15/30] hw/block/nvme: support multiple namespaces Klaus Jensen
2020-11-04 10:06 ` Max Reitz
2020-10-27 10:49 ` [PULL 16/30] pci: allocate pci id for nvme Klaus Jensen
2020-10-27 10:49 ` [PULL 17/30] hw/block/nvme: change controller pci id Klaus Jensen
2020-10-27 10:49 ` [PULL 18/30] hw/block/nvme: update nsid when registered Klaus Jensen
2020-11-04 9:32 ` Max Reitz
2020-11-04 9:52 ` Klaus Jensen
2020-10-27 10:49 ` [PULL 19/30] hw/block/nvme: remove pointless rw indirection Klaus Jensen
2020-10-27 10:49 ` [PULL 20/30] hw/block/nvme: fix log page offset check Klaus Jensen
2020-10-27 10:49 ` [PULL 21/30] hw/block/nvme: support per-namespace smart log Klaus Jensen
2020-10-27 10:49 ` [PULL 22/30] hw/block/nvme: validate command set selected Klaus Jensen
2020-10-27 10:49 ` [PULL 23/30] hw/block/nvme: support for admin-only command set Klaus Jensen
2020-10-27 10:49 ` [PULL 24/30] hw/block/nvme: reject io commands if only admin command set selected Klaus Jensen
2020-10-27 10:49 ` [PULL 25/30] hw/block/nvme: add nsid to get/setfeat trace events Klaus Jensen
2020-10-27 10:49 ` [PULL 26/30] hw/block/nvme: add trace event for requests with non-zero status code Klaus Jensen
2020-10-27 10:49 ` [PULL 27/30] hw/block/nvme: report actual LBA data shift in LBAF Klaus Jensen
2020-10-27 10:49 ` [PULL 28/30] hw/block/nvme: fix prp mapping status codes Klaus Jensen
2020-10-27 10:49 ` [PULL 29/30] hw/block/nvme: fix create IO SQ/CQ " Klaus Jensen
2020-10-27 10:49 ` [PULL 30/30] hw/block/nvme: fix queue identifer validation Klaus Jensen
2020-10-29 11:39 ` [PULL 00/30] nvme emulation patches for 5.2 Peter Maydell
2020-10-29 11:52 ` Klaus Jensen [this message]
2020-10-29 12:20 ` Philippe Mathieu-Daudé
2020-10-29 13:14 ` Klaus Jensen
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=20201029115254.GA777050@apples.localdomain \
--to=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--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 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).