From: Jarkko Sakkinen <jarkko@kernel.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "Alejandro Colomar (mailing lists,
readonly)" <alx.mailinglists@gmail.com>,
linux-man@vger.kernel.org, linux-sgx@vger.kernel.org,
dave.hansen@linux.intel.com, x86@kernel.org
Subject: Re: [PATCH] sgx.7: New page with overview of Software Guard eXtensions (SGX)
Date: Wed, 2 Dec 2020 19:27:01 +0200 [thread overview]
Message-ID: <20201202172701.GC91954@kernel.org> (raw)
In-Reply-To: <c698b115-2daa-c92b-da92-abe261a37222@gmail.com>
On Wed, Dec 02, 2020 at 03:20:09PM +0100, Michael Kerrisk (man-pages) wrote:
> Hi Jarkko,
>
> By the way, is this feature already merged into the kernel? (It
> appears not.)
No, it's not yet. Right now it's sitting in x86 tip master branch. I
thought that this is a good time to start preparing a man page given
that it's nearing completion, and also because writing man pages is new
territory for me.
I should have remarked this in the commit message. Sorry about that.
/Jarkko
next prev parent reply other threads:[~2020-12-02 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 7:15 [PATCH] sgx.7: New page with overview of Software Guard eXtensions (SGX) Jarkko Sakkinen
2020-12-02 10:37 ` Michael Kerrisk (man-pages)
2020-12-02 17:17 ` Jarkko Sakkinen
2020-12-04 1:55 ` Jarkko Sakkinen
2020-12-02 11:50 ` Alejandro Colomar (mailing lists; readonly)
2020-12-02 12:05 ` Michael Kerrisk (man-pages)
2020-12-02 14:20 ` Michael Kerrisk (man-pages)
2020-12-02 14:45 ` Alejandro Colomar (man-pages)
2020-12-02 14:47 ` Michael Kerrisk (man-pages)
2020-12-18 10:24 ` Alejandro Colomar (man-pages)
2020-12-18 12:51 ` Jarkko Sakkinen
2020-12-02 17:27 ` Jarkko Sakkinen [this message]
2020-12-02 17:21 ` Jarkko Sakkinen
2021-10-05 15:53 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=20201202172701.GC91954@kernel.org \
--to=jarkko@kernel.org \
--cc=alx.mailinglists@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=x86@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).