public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Zhichao" <zhichao.gao@intel.com>
To: gaoliming <gaoliming@byosoft.com.cn>,
	'Laszlo Ersek' <lersek@redhat.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Justen, Jordan L" <jordan.l.justen@intel.com>,
	'Ard Biesheuvel' <ard.biesheuvel@arm.com>,
	'Sami Mujawar' <sami.mujawar@arm.com>,
	"'Leif Lindholm'" <leif@nuviainc.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	"Wang, Jian J" <jian.j.wang@intel.com>,
	"Lu, XiaoyuX" <xiaoyux.lu@intel.com>,
	"Jiang, Guomin" <guomin.jiang@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Steele, Kelly" <kelly.steele@intel.com>,
	"Sun, Zailiang" <zailiang.sun@intel.com>,
	"Qian, Yi" <yi.qian@intel.com>,
	"'Maciej Rabeda'" <maciej.rabeda@linux.intel.com>,
	"Wu, Jiaxin" <jiaxin.wu@intel.com>,
	"Fu, Siyuan" <siyuan.fu@intel.com>,
	"Feng, Roger" <roger.feng@intel.com>,
	"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Re: 回复: [edk2-devel] [PATCH V3 00/12] Disable the deprecated MD5 and SHA1 support
Date: Tue, 17 Nov 2020 05:33:44 +0000	[thread overview]
Message-ID: <MWHPR11MB1647E38BFAAE9197B8ECD7D0F6E20@MWHPR11MB1647.namprd11.prod.outlook.com> (raw)
In-Reply-To: <005601d6bc31$abccbf70$03663e50$@byosoft.com.cn>

Update the patch set with required changes and R-B received on my branch: 
https://github.com/ZhichaoGao/edk2/tree/MD5_disable
And it pass the open-CI, see the result: https://github.com/tianocore/edk2/pull/1129
Maintainers,
Please help to merge.

Thanks,
Zhichao

> -----Original Message-----
> From: gaoliming <gaoliming@byosoft.com.cn>
> Sent: Tuesday, November 17, 2020 12:01 AM
> To: 'Laszlo Ersek' <lersek@redhat.com>; devel@edk2.groups.io; Gao, Zhichao
> <zhichao.gao@intel.com>
> Cc: Justen, Jordan L <jordan.l.justen@intel.com>; 'Ard Biesheuvel'
> <ard.biesheuvel@arm.com>; 'Sami Mujawar' <sami.mujawar@arm.com>; 'Leif
> Lindholm' <leif@nuviainc.com>; Yao, Jiewen <jiewen.yao@intel.com>; Wang,
> Jian J <jian.j.wang@intel.com>; Lu, XiaoyuX <xiaoyux.lu@intel.com>; Jiang,
> Guomin <guomin.jiang@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Steele, Kelly <kelly.steele@intel.com>; Sun,
> Zailiang <zailiang.sun@intel.com>; Qian, Yi <yi.qian@intel.com>; 'Maciej
> Rabeda' <maciej.rabeda@linux.intel.com>; Wu, Jiaxin <jiaxin.wu@intel.com>; Fu,
> Siyuan <siyuan.fu@intel.com>; Feng, Roger <roger.feng@intel.com>; Liu,
> Zhiguang <zhiguang.liu@intel.com>
> Subject: 回复: 回复: [edk2-devel] [PATCH V3 00/12] Disable the deprecated MD5
> and SHA1 support
> 
> Laszlo:
>   Thanks for your great support in edk2 community. You are the really role model
> as the package maintainer.
> 
>   Now, I see this patch set have got all required reviewed-by from the package
> maintainer.
>   Thanks for all package maintainers to give the quick response so that there is no
> block issue for this stable tag.
> 
>   I will continue to monitor the patch status in SFF and HFF, and try best to deliver
> the smooth stable tag release.
> 
> Thanks
> Liming
> > -----邮件原件-----
> > 发件人: Laszlo Ersek <lersek@redhat.com>
> > 发送时间: 2020年11月14日 4:05
> > 收件人: gaoliming <gaoliming@byosoft.com.cn>; devel@edk2.groups.io;
> > zhichao.gao@intel.com
> > 抄送: 'Justen, Jordan L' <jordan.l.justen@intel.com>; 'Ard Biesheuvel'
> > <ard.biesheuvel@arm.com>; 'Sami Mujawar' <sami.mujawar@arm.com>; 'Leif
> > Lindholm' <leif@nuviainc.com>; 'Yao, Jiewen' <jiewen.yao@intel.com>;
> > 'Wang, Jian J' <jian.j.wang@intel.com>; 'Lu, XiaoyuX'
> <xiaoyux.lu@intel.com>;
> > 'Jiang, Guomin' <guomin.jiang@intel.com>; 'Kinney, Michael D'
> > <michael.d.kinney@intel.com>; 'Steele, Kelly'
> > <kelly.steele@intel.com>;
> 'Sun,
> > Zailiang' <zailiang.sun@intel.com>; 'Qian, Yi' <yi.qian@intel.com>;
> 'Maciej
> > Rabeda' <maciej.rabeda@linux.intel.com>; 'Wu, Jiaxin'
> > <jiaxin.wu@intel.com>; 'Fu, Siyuan' <siyuan.fu@intel.com>; 'Feng, Roger'
> > <roger.feng@intel.com>; 'Liu, Zhiguang' <zhiguang.liu@intel.com>
> > 主题: Re: 回复: [edk2-devel] [PATCH V3 00/12] Disable the deprecated MD5
> > and SHA1 support
> >
> > On 11/13/20 07:25, gaoliming wrote:
> > > Zhichao:
> > >   I see the latest V4 version have been sent. Few days may be
> > > required
> for
> > > code review.
> > >
> > > Hi, NetworkPkg, CryptoPkg, OvmfPkg, ArmVirtPkg package maintainer
> > > and
> > > reviewer:
> > >   Because stable tag 202011 is coming soon, can you finish the code
> review
> > > for this patch set (V4 version) before Nov 17 (Next Tuesday)?
> >
> > I will do what I can, but I'm extremely annoyed that we're seeing this
> > kind of churn *again* just before the stable tag.
> >
> > If we're not ready to release edk2 at this time, the release should be
> > delayed.
> >
> > I've been reviewing various materials in 95% of my time this week. I
> > do
> > *NOT* appreciate being prodded for reviews when I'm already one of the
> > most responsive and busiest reviewers.
> >
> > Laszlo
> 
> 


      reply	other threads:[~2020-11-17  5:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1646361F135EC661.31324@groups.io>
2020-11-13  1:07 ` [edk2-devel] [PATCH V3 00/12] Disable the deprecated MD5 and SHA1 support Gao, Zhichao
2020-11-13  6:25   ` 回复: " gaoliming
2020-11-13  8:19     ` Yao, Jiewen
2020-11-13 20:04     ` 回复: " Laszlo Ersek
2020-11-16 16:00       ` 回复: " gaoliming
2020-11-17  5:33         ` Gao, Zhichao [this message]

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=MWHPR11MB1647E38BFAAE9197B8ECD7D0F6E20@MWHPR11MB1647.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