From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-man@vger.kernel.org, linux-sgx@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
nathaniel@profian.com, Michael Kerrisk <mtk.manpages@gmail.com>,
Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: [PATCH v11] sgx.7: New page with overview of Software Guard eXtensions (SGX)
Date: Wed, 9 Feb 2022 21:19:54 +0100 [thread overview]
Message-ID: <0bdb594e-7c3d-e05a-0d40-eff92b4cd252@gmail.com> (raw)
In-Reply-To: <YfNElmmBbkw1Xpfy@iki.fi>
Hi Jarkko,
On 1/28/22 02:19, Jarkko Sakkinen wrote:
> On Fri, Dec 17, 2021 at 02:50:56AM +0100, Alejandro Colomar (man-pages) wrote:
>> Hi Jarkko,
>>
>> Please see some comments below.
>>
>> Thanks,
>> Alex
>
> Thank you. I've addressed all the comments below. However, I feel that
> /dev/sgx_provision is not properly documented at all. I also think that
> Reinette's argument for v10 was fair that "remove VEPC" ioctl that QEMU
> uses should not be left out from the initial patch set.
>
> I'm implementing user space that doest attestation, so I rather write a
> proper description of the attestation, once it is working, rather than add
> to the number of review rounds.
Fair enough. Please send an v12 with those comments addressed, and I'll
merge it! (if you miss anything, we'll fix it later, don't worry)
Thanks,
Alex
next prev parent reply other threads:[~2022-02-09 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 15:33 [PATCH v11] sgx.7: New page with overview of Software Guard eXtensions (SGX) Jarkko Sakkinen
2021-12-17 1:50 ` Alejandro Colomar (man-pages)
2022-01-28 1:19 ` Jarkko Sakkinen
2022-02-09 20:19 ` Alejandro Colomar (man-pages) [this message]
2022-02-20 20:05 ` Jarkko Sakkinen
2023-03-30 22:29 ` Alejandro Colomar
2023-04-21 21:13 ` Jarkko Sakkinen
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=0bdb594e-7c3d-e05a-0d40-eff92b4cd252@gmail.com \
--to=alx.manpages@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=nathaniel@profian.com \
--cc=reinette.chatre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox