public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "kraxel@redhat.com" <kraxel@redhat.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Pawel Polawski <ppolawsk@redhat.com>,
	Brijesh Singh <brijesh.singh@amd.com>,
	Oliver Steffen <osteffen@redhat.com>,
	James Bottomley <jejb@linux.ibm.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	"Aktas, Erdem" <erdemaktas@google.com>,
	"Feng, Bob C" <bob.c.feng@intel.com>,
	"Chen, Christine" <yuwei.chen@intel.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>,
	"Xu, Min M" <min.m.xu@intel.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	"Justen, Jordan L" <jordan.l.justen@intel.com>,
	Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [edk2-devel] [PATCH v4 1/1] OvmfPkg/Sec: fix stack switch
Date: Tue, 7 Jun 2022 14:58:03 +0000	[thread overview]
Message-ID: <MW4PR11MB5872DA2FED7578CAC4F461938CA59@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220607144525.r625m3fe2koyqiyn@sirius.home.kraxel.org>

OK. Let's get it work at first.

Acked-by: Jiewen Yao <Jiewen.yao@intel.com>

> -----Original Message-----
> From: kraxel@redhat.com <kraxel@redhat.com>
> Sent: Tuesday, June 7, 2022 10:45 PM
> To: Yao, Jiewen <jiewen.yao@intel.com>
> Cc: devel@edk2.groups.io; Pawel Polawski <ppolawsk@redhat.com>; Brijesh
> Singh <brijesh.singh@amd.com>; Oliver Steffen <osteffen@redhat.com>; James
> Bottomley <jejb@linux.ibm.com>; Ard Biesheuvel <ardb+tianocore@kernel.org>;
> Aktas, Erdem <erdemaktas@google.com>; Feng, Bob C
> <bob.c.feng@intel.com>; Chen, Christine <yuwei.chen@intel.com>; Gao, Liming
> <gaoliming@byosoft.com.cn>; Xu, Min M <min.m.xu@intel.com>; Tom
> Lendacky <thomas.lendacky@amd.com>; Justen, Jordan L
> <jordan.l.justen@intel.com>; Jiri Slaby <jirislaby@kernel.org>
> Subject: Re: [edk2-devel] [PATCH v4 1/1] OvmfPkg/Sec: fix stack switch
> 
> On Tue, Jun 07, 2022 at 01:43:00PM +0000, Yao, Jiewen wrote:
> > Hello
> > As far as I know the TemporaryRamMigration() is an optional PPI according to
> PI spec, I forget why we add it in the beginning.
> 
> git log isn't very helpful here either, seems to date back to pre-git
> times without descriptive commit messages.
> 
> just commenting it out doesn't work, so probably there is some reason
> which is valid still ...
> 
> take care,
>   Gerd


  reply	other threads:[~2022-06-07 15:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 12:39 [PATCH v4 1/1] OvmfPkg/Sec: fix stack switch Gerd Hoffmann
2022-06-07 13:43 ` [edk2-devel] " Yao, Jiewen
2022-06-07 14:45   ` Gerd Hoffmann
2022-06-07 14:58     ` Yao, Jiewen [this message]
2022-06-08  6:54       ` Yao, Jiewen
2022-06-08  8:59         ` Gerd Hoffmann
2022-06-08 10:09           ` Gerd Hoffmann

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-list 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=MW4PR11MB5872DA2FED7578CAC4F461938CA59@MW4PR11MB5872.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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