On Sun, Aug 23, 2020 at 02:56:12PM +0100, Peter Maydell wrote: > On Wed, 19 Aug 2020 at 20:23, Keith Busch <kbu...@kernel.org> wrote: > > > > We're trying our first nvme pull request from a dedicated development > > tree containing various fixes, cleanups, spec compliance, and welcoming > > Klaus Jensen to maintaining the emulated nvme device development. > > > > The following changes since commit d0ed6a69d399ae193959225cdeaa9382746c91cc: > > > > Update version for v5.1.0 release (2020-08-11 17:07:03 +0100) > > > > are available in the Git repository at: > > > > git://git.infradead.org/qemu-nvme.git nvme-next > > Hi; it looks like this isn't a gpg-signed tag? > > error: remotes/nvme/nvme-next: cannot verify a non-tag object of type commit.
Oops, sorry I forgot about that part of the procedure here. The repo should have a signed tag now: The following changes since commit d0ed6a69d399ae193959225cdeaa9382746c91cc: Update version for v5.1.0 release (2020-08-11 17:07:03 +0100) are available in the Git repository at: git://git.infradead.org/qemu-nvme.git tags/for-upstream for you to fetch changes up to 9257c77e4f0feaefb76f02fff3dc8d60b420ea4d: hw/block/nvme: remove explicit qsg/iov parameters (2020-08-17 08:40:54 +0200)