From: "Klaus Jensen" <its@irrelevant.dk>
To: "Keith Busch" <kbusch@kernel.org>, "Jesper Devantier" <jwd@defmacro.it>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé via" <qemu-block@nongnu.org>,
"Fam Zheng" <fam@euphon.net>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Klaus Jensen" <k.jensen@samsung.com>
Subject: Re: [PATCH 4/5] hw/nvme: basic directives support
Date: Thu, 16 Feb 2023 18:35:27 +0100 [thread overview]
Message-ID: <f1c9dd4e-be82-415f-bd27-554962b97eb4@app.fastmail.com> (raw)
In-Reply-To: <Y+5ml5+YGC+kpU86@kbusch-mbp>
On Thu, Feb 16, 2023, at 18:23, Keith Busch wrote:
> On Thu, Feb 16, 2023 at 05:48:05PM +0100, Jesper Devantier wrote:
>> +enum NvmeDirective {
>> + NVME_DIRECTIVE_SUPPORTED = 0x0,
>> + NVME_DIRECTIVE_ENABLED = 0x1,
>> +};
>
> What's this?
That’s a left-over from my rebase. I’ll fix that one up.
next prev parent reply other threads:[~2023-02-16 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 16:48 [PATCH 0/5] Support Flexible Data Placement (FDP) Jesper Devantier
2023-02-16 16:48 ` [PATCH 1/5] hw/nvme: move adjustment of data_units{read,written} Jesper Devantier
2023-02-16 16:48 ` [PATCH 2/5] hw/nvme: store a pointer to the NvmeSubsystem in the NvmeNamespace Jesper Devantier
2023-02-16 16:48 ` [PATCH 3/5] hw/nvme: add basic endurance group support Jesper Devantier
2023-02-16 16:48 ` [PATCH 4/5] hw/nvme: basic directives support Jesper Devantier
2023-02-16 17:23 ` Keith Busch
2023-02-16 17:35 ` Klaus Jensen [this message]
2023-02-16 18:02 ` Keith Busch
2023-02-16 16:48 ` [PATCH 5/5] hw/nvme: flexible data placement emulation Jesper Devantier
2023-02-16 18:26 ` Keith Busch
2023-02-16 18:36 ` Jesper Devantier
2023-02-16 19:32 ` Keith Busch
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=f1c9dd4e-be82-415f-bd27-554962b97eb4@app.fastmail.com \
--to=its@irrelevant.dk \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=jwd@defmacro.it \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=philmd@linaro.org \
--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).