From: Christoph Hellwig <hch@infradead.org>
To: gjoyce@linux.vnet.ibm.com
Cc: keyrings@vger.kernel.org, gjoyce@ibm.com, dhowells@redhat.com,
jarkko@kernel.org, andrzej.jakowski@intel.com,
jonathan.derrick@linux.dev, drmiller.lnx@gmail.com,
linux-block@vger.kernel.org, greg@gilhooley.com
Subject: Re: [PATCH 4/4] arch_vars: create arch specific permanent store
Date: Wed, 6 Jul 2022 01:11:04 -0700 [thread overview]
Message-ID: <YsVDmPyjHLIZm+Qn@infradead.org> (raw)
In-Reply-To: <20220706023935.875994-5-gjoyce@linux.vnet.ibm.com>
On Tue, Jul 05, 2022 at 09:39:35PM -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.
Which is none as of this patch set, as is the number of of users of
this API. Did this slip in by accident?
next prev parent reply other threads:[~2022-07-06 8:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 2:39 [PATCH 0/4] sed-opal: keyrings, discovery, revert and key store gjoyce
2022-07-06 2:39 ` [PATCH 1/4] block: sed-opal: Implement IOC_OPAL_DISCOVERY gjoyce
2022-07-06 8:10 ` Christoph Hellwig
2022-07-06 2:39 ` [PATCH 2/4] block: sed-opal: Implement IOC_OPAL_REVERT_LSP gjoyce
2022-07-06 2:39 ` [PATCH 3/4] block: sed-opal: keyring support for SED Opal keys gjoyce
2022-07-06 2:39 ` [PATCH 4/4] arch_vars: create arch specific permanent store gjoyce
2022-07-06 8:11 ` Christoph Hellwig [this message]
2022-07-06 14:28 ` Greg Joyce
2022-07-06 17:10 ` kernel test robot
2022-07-08 2:35 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2022-07-18 21:01 [PATCH 0/4] sed-opal: keyrings, discovery, revert and key store gjoyce
2022-07-18 21:01 ` [PATCH 4/4] arch_vars: create arch specific permanent store gjoyce
2022-07-20 7:50 ` Christoph Hellwig
2022-07-26 18:53 ` Greg Joyce
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=YsVDmPyjHLIZm+Qn@infradead.org \
--to=hch@infradead.org \
--cc=andrzej.jakowski@intel.com \
--cc=dhowells@redhat.com \
--cc=drmiller.lnx@gmail.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).