linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: axboe@kernel.dk, linux-ide@vger.kernel.org,
	linux-nvme@lists.infradead.org
Subject: libata fixes for NVME + OPAL
Date: Wed, 24 Apr 2019 12:34:38 +0200	[thread overview]
Message-ID: <1556102081-11820-1-git-send-email-info@metux.net> (raw)

Hello folks,


here're some fixes for libata to make NVME and TCG OPAL work:

* fix a little build break in nvme (forgotten include and Kconfig select)
* introduce sysctl knob for enabling tpm stuff at runtime
  (sed-util expects since several years, so it seems that piece just might
  have been forgotten when opal support was mainlined)


--mtx

             reply	other threads:[~2019-04-24 10:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 10:34 Enrico Weigelt, metux IT consult [this message]
2019-04-24 10:34 ` [PATCH 1/3] drivers: nvme: target: core: fix build break Enrico Weigelt, metux IT consult
2019-04-24 17:07   ` Sagi Grimberg
2019-04-25  1:00   ` Chaitanya Kulkarni
2019-04-26 11:48     ` Enrico Weigelt, metux IT consult
2019-04-25 14:48   ` Christoph Hellwig
2019-04-24 10:34 ` [PATCH 2/3] drivers: libata: introduce sysctl directory Enrico Weigelt, metux IT consult
2019-04-24 10:34 ` [PATCH 3/3] drivers: libata: add sysctl: 'libata.allow_tpm' for self-encrypted devices Enrico Weigelt, metux IT consult
     [not found] ` <CGME20190424103521epcas3p44a7fc17a216b5696a6feefc781136699@epcms2p8>
2019-04-25  6:36   ` [PATCH 1/3] drivers: nvme: target: core: fix build break Minwoo Im

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=1556102081-11820-1-git-send-email-info@metux.net \
    --to=info@metux.net \
    --cc=axboe@kernel.dk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.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;
as well as URLs for NNTP newsgroup(s).