qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Klaus Jensen <its@irrelevant.dk>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
	qemu-block@nongnu.org,
	"Dmitry Fomichev" <dmitry.fomichev@wdc.com>,
	"Klaus Jensen" <k.jensen@samsung.com>,
	qemu-devel@nongnu.org, "Hanna Reitz" <hreitz@redhat.com>,
	"Keith Busch" <kbusch@kernel.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH for-7.0 0/4] hw/nvme: zoned random write area
Date: Wed, 26 Jan 2022 14:44:40 +0100	[thread overview]
Message-ID: <YfFQSKsLLqrR1Q4R@apples> (raw)
In-Reply-To: <YfFJYXZwqOGN5fX8@stefanha-x1.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

+CC Dmitry

On Jan 26 13:15, Stefan Hajnoczi wrote:
> On Wed, Jan 26, 2022 at 09:58:59AM +0100, Klaus Jensen wrote:
> > On Nov 25 08:37, Klaus Jensen wrote:
> > > From: Klaus Jensen <k.jensen@samsung.com>
> > > 
> > > This series adds support for a zoned random write area as standardized
> > > in TP 4076 ("Zoned Random Write Area").
> > > 
> > > Klaus Jensen (4):
> > >   hw/nvme: add struct for zone management send
> > >   hw/nvme: add zone attribute get/set helpers
> > >   hw/nvme: add ozcs enum
> > >   hw/nvme: add support for zoned random write area
> > > 
> > >  hw/nvme/ctrl.c       | 185 ++++++++++++++++++++++++++++++++++++-------
> > >  hw/nvme/ns.c         |  61 +++++++++++++-
> > >  hw/nvme/nvme.h       |  10 +++
> > >  hw/nvme/trace-events |   1 +
> > >  include/block/nvme.h |  43 +++++++++-
> > >  5 files changed, 271 insertions(+), 29 deletions(-)
> > > 
> > > -- 
> > > 2.34.0
> > > 
> > 
> > Bzzzzz ping :)
> 
> Hi Klaus,
> Are you pinging Keith? It's not clear from the "To:" header and I want
> to check that I'm not holding up your patches.
> 

Oh, I've never actually considered moving those that I ping to "To:",
makes sense!

And no - you are not holding up anything. I'm just pinging anyone
interested in hw/nvme (and zns).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2022-01-26 14:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25  7:37 [PATCH for-7.0 0/4] hw/nvme: zoned random write area Klaus Jensen
2021-11-25  7:37 ` [PATCH for-7.0 1/4] hw/nvme: add struct for zone management send Klaus Jensen
2022-01-26 17:00   ` Keith Busch
2021-11-25  7:37 ` [PATCH for-7.0 2/4] hw/nvme: add zone attribute get/set helpers Klaus Jensen
2022-01-26 17:05   ` Keith Busch
2021-11-25  7:37 ` [PATCH for-7.0 3/4] hw/nvme: add ozcs enum Klaus Jensen
2022-01-26 17:06   ` Keith Busch
2021-11-25  7:37 ` [PATCH for-7.0 4/4] hw/nvme: add support for zoned random write area Klaus Jensen
2022-01-26 17:09   ` Keith Busch
2022-01-26  8:58 ` [PATCH for-7.0 0/4] hw/nvme: " Klaus Jensen
2022-01-26 13:15   ` Stefan Hajnoczi
2022-01-26 13:44     ` Klaus Jensen [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=YfFQSKsLLqrR1Q4R@apples \
    --to=its@irrelevant.dk \
    --cc=dmitry.fomichev@wdc.com \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=k.jensen@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).