From: "Huang, Kai" <kai.huang@intel.com>
To: "jarkko@kernel.org" <jarkko@kernel.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>
Subject: Re: [PATCH 23/24] Documentation: x86: correct spelling
Date: Tue, 14 Feb 2023 01:23:25 +0000 [thread overview]
Message-ID: <7cf8ceb4ceaf92d3f4da9e6dbb1b88a3eca1c9f7.camel@intel.com> (raw)
In-Reply-To: <Y+XAKUjZQRByJJyL@kernel.org>
> > diff -- a/Documentation/x86/sgx.rst b/Documentation/x86/sgx.rst
> > --- a/Documentation/x86/sgx.rst
> > +++ b/Documentation/x86/sgx.rst
> > @@ -245,7 +245,7 @@ SGX will likely become unusable because
> > limited. However, while this may be fatal to SGX, the rest of the kernel
> > is unlikely to be impacted and should continue to work.
> >
> > -As a result, when this happpens, user should stop running any new
> > +As a result, when this happens, the user should stop running any new
> > SGX workloads, (or just any new workloads), and migrate all valuable
> > workloads. Although a machine reboot can recover all EPC memory, the bug
> > should be reported to Linux developers.
>
>
> Acked-by: Jarkko Sakkinen <jarkko@kernel.org>
>
> BR, Jarkko
For SGX part:
Acked-by: Kai Huang <kai.huang@intel.com>
next prev parent reply other threads:[~2023-02-14 1:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 7:13 [PATCH 00/24 v2] Documentation: correct lots of spelling errors (series 1) Randy Dunlap
2023-02-09 7:13 ` [PATCH 23/24] Documentation: x86: correct spelling Randy Dunlap
2023-02-09 23:22 ` Reinette Chatre
2023-02-10 3:55 ` Jarkko Sakkinen
2023-02-14 1:23 ` Huang, Kai [this message]
2023-02-10 4:19 ` Fenghua Yu
2023-02-11 0:30 ` [PATCH 00/24 v2] Documentation: correct lots of spelling errors (series 1) patchwork-bot+netdevbpf
2023-06-26 6:56 ` Krzysztof Wilczyński
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=7cf8ceb4ceaf92d3f4da9e6dbb1b88a3eca1c9f7.camel@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=fenghua.yu@intel.com \
--cc=jarkko@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--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).