[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7cf8ceb4ceaf92d3f4da9e6dbb1b88a3eca1c9f7.camel@intel.com>
Date: Tue, 14 Feb 2023 01:23:25 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "jarkko@...nel.org" <jarkko@...nel.org>,
"rdunlap@...radead.org" <rdunlap@...radead.org>
CC: "corbet@....net" <corbet@....net>,
"linux-sgx@...r.kernel.org" <linux-sgx@...r.kernel.org>,
"bp@...en8.de" <bp@...en8.de>, "x86@...nel.org" <x86@...nel.org>,
"Chatre, Reinette" <reinette.chatre@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>
Subject: Re: [PATCH 23/24] Documentation: x86: correct spelling
> > 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@...nel.org>
>
> BR, Jarkko
For SGX part:
Acked-by: Kai Huang <kai.huang@...el.com>
Powered by blists - more mailing lists