Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: Block ns inventory changes during admin
Date: Mon, 28 Jan 2019 16:58:34 +0100	[thread overview]
Message-ID: <20190128155834.GA11346@lst.de> (raw)
In-Reply-To: <20190128153344.GA15271@localhost.localdomain>

On Mon, Jan 28, 2019@08:33:45AM -0700, Keith Busch wrote:
> This was reported internally from Wen. If you prefer, we can open a
> public bz sighting and append the kernel logs for a changelog Link:.

I don't really need a bugzilla, but I'd like to understand the reported
problem a little better.

  reply	other threads:[~2019-01-28 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 19:48 [PATCH] nvme: Block ns inventory changes during admin Keith Busch
     [not found] ` <OF5147C249.BC64CC03-ON0025838D.007F28EE-8625838D.007F6785@notes.na.collabserv.com>
2019-01-25 23:37   ` Keith Busch
     [not found]     ` <BYAPR04MB45021C05936FF7EF982D579686940@BYAPR04MB4502.namprd04.prod.outlook.com>
2019-01-28 15:36       ` Keith Busch
2019-01-28  7:39 ` Christoph Hellwig
2019-01-28 15:33   ` Keith Busch
2019-01-28 15:58     ` Christoph Hellwig [this message]
2019-01-28 16:07       ` Keith Busch
2019-01-28 16:30         ` Christoph Hellwig

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=20190128155834.GA11346@lst.de \
    --to=hch@lst.de \
    /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