From: Randy Dunlap <rdunlap@infradead.org>
To: Russ Weight <russell.h.weight@intel.com>,
mdf@kernel.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: trix@redhat.com, lgoncalv@redhat.com, yilun.xu@intel.com,
hao.wu@intel.com, matthew.gerlach@intel.com
Subject: Re: [PATCH v7 1/7] fpga: sec-mgr: fpga security manager class driver
Date: Fri, 4 Dec 2020 11:45:54 -0800 [thread overview]
Message-ID: <711e290a-d8de-b31a-d640-df6785a3eba3@infradead.org> (raw)
In-Reply-To: <20201203210958.241329-2-russell.h.weight@intel.com>
Hi--
On 12/3/20 1:09 PM, Russ Weight wrote:
> ---
> diff --git a/Documentation/fpga/fpga-sec-mgr.rst b/Documentation/fpga/fpga-sec-mgr.rst
> new file mode 100644
> index 000000000000..26dac599ead7
> --- /dev/null
> +++ b/Documentation/fpga/fpga-sec-mgr.rst
> @@ -0,0 +1,44 @@
> +In addition to managing secure updates of the FPGA and BMC images,
> +the FPGA Security Manager update process may also used to
may also be used to
> +program root entry hashes and cancellation keys for the FPGA static
> +region, the FPGA partial reconfiguration region, and the BMC.
thanks.
--
~Randy
next prev parent reply other threads:[~2020-12-04 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 21:09 [PATCH v7 0/7] FPGA Security Manager Class Driver Russ Weight
2020-12-03 21:09 ` [PATCH v7 1/7] fpga: sec-mgr: fpga security manager class driver Russ Weight
2020-12-04 19:45 ` Randy Dunlap [this message]
2020-12-07 18:09 ` Russ Weight
2020-12-03 21:09 ` [PATCH v7 2/7] fpga: sec-mgr: enable secure updates Russ Weight
2020-12-03 21:09 ` [PATCH v7 3/7] fpga: sec-mgr: expose sec-mgr update status Russ Weight
2020-12-03 21:09 ` [PATCH v7 4/7] fpga: sec-mgr: expose sec-mgr update errors Russ Weight
2020-12-03 21:09 ` [PATCH v7 5/7] fpga: sec-mgr: expose sec-mgr update size Russ Weight
2020-12-03 21:09 ` [PATCH v7 6/7] fpga: sec-mgr: enable cancel of secure update Russ Weight
2020-12-03 21:09 ` [PATCH v7 7/7] fpga: sec-mgr: expose hardware error info Russ Weight
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=711e290a-d8de-b31a-d640-df6785a3eba3@infradead.org \
--to=rdunlap@infradead.org \
--cc=hao.wu@intel.com \
--cc=lgoncalv@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@intel.com \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
/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.