public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, yi1.li@intel.com
Cc: "Wang, Jian J" <jian.j.wang@intel.com>,
	"Lu, Xiaoyu1" <xiaoyu1.lu@intel.com>,
	"Jiang, Guomin" <guomin.jiang@intel.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH] CryptoPkg: Add b_print.c which removed floating-point to OpensslLib
Date: Mon, 21 Nov 2022 10:21:53 +0100	[thread overview]
Message-ID: <20221121092153.p4umhcaptgoxf3ra@sirius.home.kraxel.org> (raw)
In-Reply-To: <SJ1PR11MB6227960A77C71117E9900EBCC50A9@SJ1PR11MB6227.namprd11.prod.outlook.com>

On Mon, Nov 21, 2022 at 08:31:19AM +0000, Li, Yi wrote:
> Hi Gerd,
> 
> Cool! I noticed your patch in openssl3.0 branch.
> Because the Tls cert time check needs to be solved as soon as possible,
> I will cherry-pick your patch to 1.1.1 branch instead of updating edk2 openssl to 3.0. The latter seems to take a long time.
> 
> By the way, I remember you are already working on upstream openssl3.0, right?

Tried, yes (that's why it is fixed already in upstream openssl3).

> How is it doing now, I can help with some work if needed.

The blocker is that openssl 3 noticeable larger than the 1.1.1 version.
Which is according to Jiewen Yao not acceptable because it wouldn't
fit into the flash layout for existing roms.

I don't have any good idea how to move forward with this.  My old WIP
branch is here:

https://github.com/kraxel/edk2/commits/archive/openssl3-v1

take care,
  Gerd


  reply	other threads:[~2022-11-21  9:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19 16:27 [PATCH] CryptoPkg: Add b_print.c which removed floating-point to OpensslLib Li, Yi
2022-11-19 16:32 ` Li, Yi
2022-11-20  2:18   ` Yao, Jiewen
2022-11-20  4:30     ` Li, Yi
2022-11-21  6:23     ` [edk2-devel] " Gerd Hoffmann
2022-11-21  8:31       ` Li, Yi
2022-11-21  9:21         ` Gerd Hoffmann [this message]
2022-11-21 13:18           ` Yao, Jiewen

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=20221121092153.p4umhcaptgoxf3ra@sirius.home.kraxel.org \
    --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