From: Klaus Jensen <its@irrelevant.dk>
To: Joelle van Dyne <j@getutm.app>
Cc: Keith Busch <kbusch@kernel.org>, Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, "open list:nvme" <qemu-block@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH] nvme: expose 'bootindex' property
Date: Tue, 30 Mar 2021 20:10:15 +0200 [thread overview]
Message-ID: <YGNph1nPr/fY00Nq@apples.localdomain> (raw)
In-Reply-To: <20210322082444.12916-1-j@getutm.app>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Mar 22 01:24, Joelle van Dyne wrote:
> The check for `n->namespace.blkconf.blk` always fails because
> this is in the initialization function.
>
> Signed-off-by: Joelle van Dyne <j@getutm.app>
> ---
> hw/block/nvme.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/hw/block/nvme.c b/hw/block/nvme.c
> index 6842b01ab5..42605fc55d 100644
> --- a/hw/block/nvme.c
> +++ b/hw/block/nvme.c
> @@ -6330,11 +6330,9 @@ static void nvme_instance_init(Object *obj)
> {
> NvmeCtrl *n = NVME(obj);
>
> - if (n->namespace.blkconf.blk) {
> - device_add_bootindex_property(obj, &n->namespace.blkconf.bootindex,
> - "bootindex", "/namespace@1,0",
> - DEVICE(obj));
> - }
> + device_add_bootindex_property(obj, &n->namespace.blkconf.bootindex,
> + "bootindex", "/namespace@1,0",
> + DEVICE(obj));
>
> object_property_add(obj, "smart_critical_warning", "uint8",
> nvme_get_smart_warning,
> --
> 2.28.0
>
Applied on nvme-fixes, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-30 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 8:24 [PATCH] nvme: expose 'bootindex' property Joelle van Dyne
2021-03-22 9:58 ` Philippe Mathieu-Daudé
2021-03-22 12:37 ` Klaus Jensen
2021-03-22 13:10 ` Philippe Mathieu-Daudé
2021-03-22 13:19 ` Klaus Jensen
2021-03-30 18:10 ` 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=YGNph1nPr/fY00Nq@apples.localdomain \
--to=its@irrelevant.dk \
--cc=j@getutm.app \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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 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.