qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Klaus Jensen <its@irrelevant.dk>
Cc: Hannes Reinecke <hare@suse.de>, Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org,
	Keith Busch <keith.busch@wdc.com>
Subject: Re: [PATCH] hw/block/nvme: re-enable NVMe PCI hotplug
Date: Tue, 18 Oct 2022 10:15:46 +0200	[thread overview]
Message-ID: <20221018081546.mzziix5ymjmpus56@carbon.lan> (raw)
In-Reply-To: <Y0RTHArVOWN2Tg2K@cormorant.local>

On Mon, Oct 10, 2022 at 07:15:08PM +0200, Klaus Jensen wrote:
> This is all upstream. Namespaces with 'shared=on' *should* all be
> automatically attached to any hotplugged controller devices.
> 
> With what setup is this not working for you?

Ah okay, I missed the 'shared=on' bit. Let me try again.



  reply	other threads:[~2022-10-18  8:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11  7:35 [PATCH] hw/block/nvme: re-enable NVMe PCI hotplug Hannes Reinecke
2021-05-11  7:45 ` no-reply
2021-05-11  8:05 ` Philippe Mathieu-Daudé
2021-05-11 12:22 ` Klaus Jensen
2021-05-11 13:12   ` Hannes Reinecke
2021-05-11 13:37     ` Klaus Jensen
2021-05-11 14:54       ` Hannes Reinecke
2021-05-11 16:03         ` Klaus Jensen
2021-05-11 16:12           ` Hannes Reinecke
2022-10-10 17:01             ` Daniel Wagner
2022-10-10 17:15               ` Klaus Jensen
2022-10-18  8:15                 ` Daniel Wagner [this message]
2022-10-21 12:59                   ` Daniel Wagner
2022-10-31  7:30                     ` Klaus Jensen
2022-10-12  6:24               ` Hannes Reinecke
2022-10-12  8:06                 ` 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=20221018081546.mzziix5ymjmpus56@carbon.lan \
    --to=wagi@monom.org \
    --cc=hare@suse.de \
    --cc=its@irrelevant.dk \
    --cc=keith.busch@wdc.com \
    --cc=kwolf@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 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).