From: Christoph Hellwig <hch@infradead.org>
To: gjoyce@linux.vnet.ibm.com
Cc: linux-block@vger.kernel.org, keyrings@vger.kernel.org,
dhowells@redhat.com, jarkko@kernel.org,
jonathan.derrick@linux.dev, brking@linux.vnet.ibm.com,
greg@gilhooley.com, gjoyce@ibm.com
Subject: Re: [PATCH 4/4] arch_vars: create arch specific permanent store
Date: Wed, 20 Jul 2022 00:50:17 -0700 [thread overview]
Message-ID: <YtezuVYVQnqX2IsY@infradead.org> (raw)
In-Reply-To: <20220718210156.1535955-5-gjoyce@linux.vnet.ibm.com>
On Mon, Jul 18, 2022 at 04:01:56PM -0500, gjoyce@linux.vnet.ibm.com wrote:
> From: Greg Joyce <gjoyce@linux.vnet.ibm.com>
>
> Platforms that have a permanent key store may provide unique
> platform dependent functions to read/write variables. The
> default (weak) functions return -EOPNOTSUPP unless overridden
> by architecture/platform versions.
This is still lacking any useful implementation. It also seems to be
used in patch 3 before it actually is used.
As the functionality seems optional I'd suggest to drop this patch for
now and not call it from patch 3, and do a separate series later that
adds the infrastructure, at leat one useful backend and the caller.
next prev parent reply other threads:[~2022-07-20 7:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 21:01 [PATCH 0/4] sed-opal: keyrings, discovery, revert and key store gjoyce
2022-07-18 21:01 ` [PATCH 1/4] block: sed-opal: Implement IOC_OPAL_DISCOVERY gjoyce
2022-07-20 7:42 ` Christoph Hellwig
2022-07-18 21:01 ` [PATCH 2/4] block: sed-opal: Implement IOC_OPAL_REVERT_LSP gjoyce
2022-07-20 7:44 ` Christoph Hellwig
2022-07-18 21:01 ` [PATCH 3/4] block: sed-opal: keyring support for SED Opal keys gjoyce
2022-07-19 6:49 ` Hannes Reinecke
2022-07-20 7:49 ` Christoph Hellwig
2022-07-18 21:01 ` [PATCH 4/4] arch_vars: create arch specific permanent store gjoyce
2022-07-20 7:50 ` Christoph Hellwig [this message]
2022-07-26 18:53 ` Greg Joyce
2022-07-28 7:43 ` [PATCH 0/4] sed-opal: keyrings, discovery, revert and key store Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2022-07-06 2:39 gjoyce
2022-07-06 2:39 ` [PATCH 4/4] arch_vars: create arch specific permanent store gjoyce
2022-07-06 8:11 ` Christoph Hellwig
2022-07-06 14:28 ` Greg Joyce
2022-07-06 17:10 ` kernel test robot
2022-07-08 2:35 ` kernel test robot
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=YtezuVYVQnqX2IsY@infradead.org \
--to=hch@infradead.org \
--cc=brking@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=gjoyce@ibm.com \
--cc=gjoyce@linux.vnet.ibm.com \
--cc=greg@gilhooley.com \
--cc=jarkko@kernel.org \
--cc=jonathan.derrick@linux.dev \
--cc=keyrings@vger.kernel.org \
--cc=linux-block@vger.kernel.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).