From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: Register for ANA AEN
Date: Thu, 26 Jul 2018 17:12:21 +0200 [thread overview]
Message-ID: <20180726151221.GA7791@lst.de> (raw)
In-Reply-To: <763ec760-8651-ff20-fe01-00ab43f29337@suse.de>
On Thu, Jul 26, 2018@03:37:48PM +0200, Hannes Reinecke wrote:
> > I'll send out another round later today.
> >
> Would it make sense to read back the features after we've tried to
> enable them?
> It might be that the target doesn't enable ANA AENs (or doesn't support
> them), at which point we have to disable ANA on the host as we rely on
> ANA AENs for correct operations ...
If it doesn't support the AEN it won't be in OAES..
prev parent reply other threads:[~2018-07-26 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 10:55 [PATCH] nvme: Register for ANA AEN Hannes Reinecke
2018-07-26 10:58 ` Hannes Reinecke
2018-07-26 11:59 ` Christoph Hellwig
2018-07-26 12:01 ` Christoph Hellwig
2018-07-26 12:02 ` Hannes Reinecke
2018-07-26 12:07 ` Christoph Hellwig
2018-07-26 13:37 ` Hannes Reinecke
2018-07-26 15:12 ` Christoph Hellwig [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=20180726151221.GA7791@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