From: "Laszlo Ersek" <lersek@redhat.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
"Zurcher, Christopher J" <christopher.j.zurcher@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
gaoliming <gaoliming@byosoft.com.cn>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Lu, XiaoyuX" <xiaoyux.lu@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>
Subject: Re: [edk2-devel] [PATCH v5 0/2] CryptoPkg/OpensslLib: Add native instruction support for X64
Date: Wed, 11 Nov 2020 20:09:07 +0100 [thread overview]
Message-ID: <8bb817f1-d473-467a-f33e-a3c22a79528b@redhat.com> (raw)
In-Reply-To: <CY4PR11MB128800913F53489ACE69BB748CE80@CY4PR11MB1288.namprd11.prod.outlook.com>
On 11/11/20 03:19, Yao, Jiewen wrote:
> I full agree with long term plan. E.g. we need remove ApiHook.c as well.
>
> I more concern about the short term plan, if you want to check in this and get the capability.
>
> I think we need this capability for GCC tool chain as well, so I am OK to check in .S.
> This is auto generated. I do not think it is a step back.
>
> We can remove them together with ApiHook later, in the long term.
Agreed on all counts.
Laszlo
next prev parent reply other threads:[~2020-11-11 19:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 21:58 [PATCH v5 0/2] CryptoPkg/OpensslLib: Add native instruction support for X64 Zurcher, Christopher J
2020-11-03 21:58 ` [PATCH v5 1/2] " Zurcher, Christopher J
2020-11-03 21:58 ` [PATCH v5 2/2] CryptoPkg/OpensslLib: Commit the auto-generated assembly files " Zurcher, Christopher J
2020-11-06 5:56 ` [PATCH v5 0/2] CryptoPkg/OpensslLib: Add native instruction support " Yao, Jiewen
[not found] ` <1644D590FF4B7423.25549@groups.io>
2020-11-06 6:13 ` [edk2-devel] " Yao, Jiewen
2020-11-06 9:50 ` Zurcher, Christopher J
2020-11-06 10:22 ` Yao, Jiewen
2020-11-06 19:35 ` Zurcher, Christopher J
2020-11-06 23:06 ` Yao, Jiewen
2020-11-07 2:02 ` Zurcher, Christopher J
2020-11-07 2:24 ` Yao, Jiewen
2020-11-07 7:26 ` Michael D Kinney
2020-11-10 12:31 ` Laszlo Ersek
2020-11-10 14:28 ` 回复: " gaoliming
2020-11-11 19:05 ` Laszlo Ersek
2020-11-10 17:07 ` Yao, Jiewen
2020-11-11 1:43 ` Zurcher, Christopher J
2020-11-11 2:19 ` Yao, Jiewen
2020-11-11 19:09 ` Laszlo Ersek [this message]
2020-11-13 1:22 ` Zurcher, Christopher J
[not found] ` <1646ECAE89844BF6.31886@groups.io>
2020-11-13 2:28 ` Zurcher, Christopher J
2020-11-13 7:35 ` Ard Biesheuvel
2020-11-13 20:02 ` Laszlo Ersek
2020-11-11 19:08 ` Laszlo Ersek
2020-11-11 19:07 ` Laszlo Ersek
2020-11-09 7:03 ` 回复: " gaoliming
2020-11-10 12:24 ` Laszlo Ersek
2020-11-09 6:56 ` 回复: " gaoliming
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=8bb817f1-d473-467a-f33e-a3c22a79528b@redhat.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