All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Klaus Jensen <k.jensen@samsung.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Klaus Jensen <its@irrelevant.dk>
Subject: Re: [PULL] nvme updates
Date: Wed, 26 Aug 2020 05:12:42 +0900	[thread overview]
Message-ID: <20200825201242.GA20971@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <CAFEAcA8-VgEDTZ7+T9ZgB2LR9KWRrejBtZN=iwy2GGPcuFuz2Q@mail.gmail.com>

On Sun, Aug 23, 2020 at 02:56:12PM +0100, Peter Maydell wrote:
> On Wed, 19 Aug 2020 at 20:23, Keith Busch <kbusch@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)


  reply	other threads:[~2020-08-25 20:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 19:22 [PULL] nvme updates Keith Busch
2020-08-23 13:56 ` Peter Maydell
2020-08-25 20:12   ` Keith Busch [this message]
2020-08-25 21:43     ` Peter Maydell
2020-08-25 22:28       ` Keith Busch
2020-08-26  5:51         ` 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=20200825201242.GA20971@redsun51.ssa.fujisawa.hgst.com \
    --to=kbusch@kernel.org \
    --cc=its@irrelevant.dk \
    --cc=k.jensen@samsung.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.