public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wang, Jian J" <jian.j.wang@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"Bi, Dandan" <dandan.bi@intel.com>,
	"Wu, Hao A" <hao.a.wu@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Laszlo Ersek <lersek@redhat.com>,
	Leif Lindholm <leif@nuviainc.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Ni, Ray" <ray.ni@intel.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: Re: [edk2-devel] [PATCH 0/4] remove generation of EFI properties table
Date: Tue, 7 Apr 2020 07:27:22 +0000	[thread overview]
Message-ID: <D827630B58408649ACB04F44C510003625A45B62@SHSMSX107.ccr.corp.intel.com> (raw)
In-Reply-To: <CAKv+Gu8rBN8061H7224xsaKXtGehZQJGC8B7wAbPO9QsX3jgfA@mail.gmail.com>

Ard,

My apologies. I was indeed working desperately to catch some deadlines recently.
I agree to remove the properties table.

For the whole series, 

Reviewed-by: Jian J Wang <jian.j.wang@intel.com>

Regards,
Jian

> -----Original Message-----
> From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Sent: Monday, April 06, 2020 7:42 PM
> To: Bi, Dandan <dandan.bi@intel.com>; Wang, Jian J <jian.j.wang@intel.com>;
> Wu, Hao A <hao.a.wu@intel.com>
> Cc: devel@edk2.groups.io; Laszlo Ersek <lersek@redhat.com>; Leif Lindholm
> <leif@nuviainc.com>; Kinney, Michael D <michael.d.kinney@intel.com>; Ni, Ray
> <ray.ni@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>; Bret Barkelew
> <Bret.Barkelew@microsoft.com>
> Subject: Re: [edk2-devel] [PATCH 0/4] remove generation of EFI properties table
> 
> On Fri, 3 Apr 2020 at 04:22, Bi, Dandan <dandan.bi@intel.com> wrote:
> >
> > For the functionality, it is the same with before for platforms which set
> PcdPropertiesTableEnable to false by default.
> > Reviewed-by: Dandan Bi <dandan.bi@intel.com> for patch [PATCH 2/4]
> [PATCH 3/4] [PATCH 4/4].
> >
> >
> > If anyone still has the use case of enabling PcdPropertiesTableEnable, please
> comment.
> >
> 
> Thank you Dandan.
> 
> Jian, Hao, do you have any comments on this series? If you are too
> busy to have a closer look immediately, could you please indicate so
> instead of not responding at all? Thanks.

  reply	other threads:[~2020-04-07  7:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 10:24 [PATCH 0/4] remove generation of EFI properties table Ard Biesheuvel
2020-03-26 10:24 ` [PATCH 1/4] OvmfPkg: remove handling of " Ard Biesheuvel
2020-03-27 14:01   ` [edk2-devel] " Laszlo Ersek
2020-03-26 10:24 ` [PATCH 2/4] MdeModulePkg: disable properties table generation but retain the code Ard Biesheuvel
2020-03-26 10:24 ` [PATCH 3/4] MdePkg: remove PropertiesTable GUID Ard Biesheuvel
2020-03-27  1:02   ` [EXTERNAL] " Bret Barkelew
2020-03-27  9:16     ` Ard Biesheuvel
2020-03-26 10:24 ` [PATCH 4/4] MdeModulePkg/DxeCore: merge properties table routines into MAT handling Ard Biesheuvel
2020-03-27  5:00 ` [PATCH 0/4] remove generation of EFI properties table Yao, Jiewen
2020-03-30 13:42   ` [edk2-devel] " Liming Gao
2020-03-30 17:57     ` Ard Biesheuvel
2020-04-01 17:17       ` Ard Biesheuvel
2020-04-03  2:22 ` Dandan Bi
2020-04-06 11:42   ` Ard Biesheuvel
2020-04-07  7:27     ` Wang, Jian J [this message]
2020-04-07  8:22       ` Ard Biesheuvel

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=D827630B58408649ACB04F44C510003625A45B62@SHSMSX107.ccr.corp.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