From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-ioctl: clear rae for discovery log pages
Date: Wed, 12 Dec 2018 09:29:26 +0100 [thread overview]
Message-ID: <20181212082926.GB29996@lst.de> (raw)
In-Reply-To: <20181207220530.30310-1-sagi@grimberg.me>
On Fri, Dec 07, 2018@02:05:30PM -0800, Sagi Grimberg wrote:
> The discovery controller should now be able to send
> us discovery log change events so we need to clear the
> rae bit for that.
Btw, I really think we need to clear the RAE bit in the kernel with
a small whitelist for those AENs that we pass on to userspace so that
we don't accidentally get the bit cleared. What do you think?
next prev parent reply other threads:[~2018-12-12 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 22:05 [PATCH] nvme-ioctl: clear rae for discovery log pages Sagi Grimberg
2018-12-07 22:16 ` Keith Busch
2018-12-12 8:29 ` Christoph Hellwig [this message]
2018-12-13 16:44 ` Sagi Grimberg
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=20181212082926.GB29996@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