From: "cbduggap" <chinni.b.duggapu@intel.com>
To: devel@edk2.groups.io
Subject: [PATCH v5 0/2] FSP_TEMP_RAM_INIT call must follow X64 Calling Convention
Date: Tue, 17 May 2022 14:13:59 +0530 [thread overview]
Message-ID: <20220517084401.1805-1-chinni.b.duggapu@intel.com> (raw)
cbduggap (2):
IntelFsp2Pkg: FSP_TEMP_RAM_INIT call must follow X64 Calling
Convention
IntelFsp2WrapperPkg: FSP_TEMP_RAM_INIT call must follow X64 Calling
Convention
IntelFsp2Pkg/FspSecCore/X64/FspApiEntryT.nasm | 39 ++++++++++---------
.../Include/SaveRestoreSseAvxNasm.inc | 28 +++++++++++++
.../X64/SecEntry.nasm | 4 +-
3 files changed, 51 insertions(+), 20 deletions(-)
--
2.36.0.windows.1
next reply other threads:[~2022-05-17 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 8:43 cbduggap [this message]
2022-05-17 8:44 ` [PATCH v5 1/2] IntelFsp2Pkg: FSP_TEMP_RAM_INIT call must follow X64 Calling Convention cbduggap
2022-05-18 1:40 ` Chiu, Chasel
2022-05-17 8:44 ` [PATCH v5 2/2] IntelFsp2WrapperPkg: " cbduggap
2022-05-18 1:41 ` Chiu, Chasel
2022-05-18 2:41 ` [edk2-devel] " Kuo, Ted
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=20220517084401.1805-1-chinni.b.duggapu@intel.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