All of lore.kernel.org
 help / color / mirror / Atom feed
From: j.naumann@fu-berlin.de (Jan Luca Naumann)
Subject: Problem with new uapi header in Linux kernel 4.4+
Date: Sat, 8 Oct 2016 12:23:16 +0200	[thread overview]
Message-ID: <a05d526b-f392-4639-68dc-5c4267ccb26f@fu-berlin.de> (raw)
In-Reply-To: <20161007143101.GA5899@sbauer-Z170X-UD5>

Hey,

this sound very nice :-) OPAL supported directly by the kernel would be
very good.

Thank you and best regards,
Jan

Am 07.10.2016 um 16:31 schrieb Scott Bauer:
> On Fri, Oct 07, 2016@12:31:11AM -0700, Christoph Hellwig wrote:
>> 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).
> 
> I or Rafael will send a series sometime next week or early the week after...
> assuming some final testing all goes to plan.
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20161008/5c79dae2/attachment.sig>

      reply	other threads:[~2016-10-08 10:23 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
2016-10-07 14:31     ` Scott Bauer
2016-10-08 10:23       ` Jan Luca Naumann [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=a05d526b-f392-4639-68dc-5c4267ccb26f@fu-berlin.de \
    --to=j.naumann@fu-berlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.