From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Chen, Gang C" <gang.c.chen@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Wang, Jian J" <jian.j.wang@intel.com>
Subject: Re: [PATCH] CryptoPkg/OpensslLib: Upgrade OpenSSL to 1.1.1s
Date: Fri, 18 Nov 2022 08:10:47 +0000 [thread overview]
Message-ID: <MW4PR11MB58727B633A750DF1B1CA121C8C099@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CH0PR11MB569011A1F9A4570997B4EDE8A3099@CH0PR11MB5690.namprd11.prod.outlook.com>
Sounds good. No size different is good news.
Reviewed-by: Jiewen Yao <Jiewen.yao@intel.com>
We are in hard-freeze now. This will be merged after freeze.
Thank you
Yao Jiewen
> -----Original Message-----
> From: Chen, Gang C <gang.c.chen@intel.com>
> Sent: Friday, November 18, 2022 4:08 PM
> To: Yao, Jiewen <jiewen.yao@intel.com>; devel@edk2.groups.io
> Cc: Wang, Jian J <jian.j.wang@intel.com>
> Subject: RE: [PATCH] CryptoPkg/OpensslLib: Upgrade OpenSSL to 1.1.1s
>
> Hi Jiewen,
>
> Thanks for your review.
>
> Yes, I did finish the tiano CI: https://github.com/tianocore/edk2/pull/3648.
>
> Regarding the size, I'm not sure which lib you'd like to know. So I list the 3
> CryptLib size here(compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0):
>
> PeiCryptLib.lib BaseCryptLib.lib
> SmmCryptLib.lib
> 1.1.1n 645426 973132
> 908298
> 1.1.1s 645402 973140 908298
>
> Thanks.
>
> Best Regards
> Gang
>
> -----Original Message-----
> From: Yao, Jiewen <jiewen.yao@intel.com>
> Sent: Thursday, November 17, 2022 5:32 PM
> To: Chen, Gang C <gang.c.chen@intel.com>; devel@edk2.groups.io
> Cc: Wang, Jian J <jian.j.wang@intel.com>; Yao, Jiewen
> <jiewen.yao@intel.com>
> Subject: RE: [PATCH] CryptoPkg/OpensslLib: Upgrade OpenSSL to 1.1.1s
>
> Hi
> Have you run the tiano CI ?
>
> Would you please share the size data before and after?
>
> Thank you
> Yao, Jiewen
>
> > -----Original Message-----
> > From: Chen, Gang C <gang.c.chen@intel.com>
> > Sent: Thursday, November 17, 2022 4:40 PM
> > To: devel@edk2.groups.io
> > Cc: Yao, Jiewen <jiewen.yao@intel.com>; Wang, Jian J
> > <jian.j.wang@intel.com>; Chen, Gang C <gang.c.chen@intel.com>
> > Subject: [PATCH] CryptoPkg/OpensslLib: Upgrade OpenSSL to 1.1.1s
> >
> > Upgrade openssl to 1.1.1s.
> >
> > Pick up bugfixes from the latest openssl release, which include some
> > GCC build warnings cleaning up.
> >
> > Cc: Jian J Wang <jian.j.wang@intel.com>
> > Cc: Jiewen Yao <jiewen.yao@intel.com>
> > Signed-off-by: Gang Chen <gang.c.chen@intel.com>
> > ---
> > CryptoPkg/Library/OpensslLib/openssl | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/CryptoPkg/Library/OpensslLib/openssl
> > b/CryptoPkg/Library/OpensslLib/openssl
> > index d82e959e62..129058165d 160000
> > --- a/CryptoPkg/Library/OpensslLib/openssl
> > +++ b/CryptoPkg/Library/OpensslLib/openssl
> > @@ -1 +1 @@
> > -Subproject commit d82e959e621a3d597f1e0d50ff8c2d8b96915fd7
> > +Subproject commit 129058165d195e43a0ad10111b0c2e29bdf65980
> > --
> > 2.38.0
next prev parent reply other threads:[~2022-11-18 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 8:39 [PATCH] CryptoPkg/OpensslLib: Upgrade OpenSSL to 1.1.1s Chen, Gang C
2022-11-17 9:31 ` Yao, Jiewen
2022-11-18 8:07 ` Chen, Gang C
2022-11-18 8:10 ` Yao, Jiewen [this message]
[not found] ` <17289F83EB119B25.25323@groups.io>
2022-12-01 9:31 ` [edk2-devel] " 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=MW4PR11MB58727B633A750DF1B1CA121C8C099@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