Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: Problem with new uapi header in Linux kernel 4.4+
Date: Fri, 7 Oct 2016 00:31:11 -0700	[thread overview]
Message-ID: <20161007073111.GB1936@infradead.org> (raw)
In-Reply-To: <C17953214F1EE04D9E8A11E8F3E869F051C4F9@ORSMSX110.amr.corp.intel.com>

Hi Scott,

> For what it is worth the kernel will soon have OPAL support built in 
> so you won't have to do this weird hack, and use a tool that is no
> longer maintained. 

What's the ETA for OPAL support?  We had a patch from Intel for it
half a year ago, but the submitter didn't follow up on the review
feedback.  (Same for the simple ATA security unlock scheme submitted
by someone else).

  reply	other threads:[~2016-10-07  7:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 15:15 Problem with new uapi header in Linux kernel 4.4+ Jan Luca Naumann
2016-10-06 23:09 ` Keith Busch
2016-10-07  7:29   ` Christoph Hellwig
2016-10-07 10:06     ` Jan Luca Naumann
2016-10-06 23:28 ` Bauer, Scott
2016-10-07  7:31   ` Christoph Hellwig [this message]
2016-10-07 14:31     ` Scott Bauer
2016-10-08 10:23       ` Jan Luca Naumann

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=20161007073111.GB1936@infradead.org \
    --to=hch@infradead.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