public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sami Mujawar" <sami.mujawar@arm.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"zhichao.gao@intel.com" <zhichao.gao@intel.com>
Cc: "tomas@nuviainc.com" <tomas@nuviainc.com>,
	Matteo Carlini <Matteo.Carlini@arm.com>
Subject: Re: [edk2-devel] acpiview error handling patches
Date: Tue, 11 Aug 2020 13:45:20 +0000	[thread overview]
Message-ID: <DB7PR08MB309778463494E31D8CE2B94784450@DB7PR08MB3097.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <DM6PR11MB4425292778BA0CC9BBE60BDEF64E0@DM6PR11MB4425.namprd11.prod.outlook.com>

Hi Zhichao,

Some patches in this series need reworking.

Example - For '[PATCH v3 1/8] ShellPkg/AcpiView: Extract configuration struct' & '[PATCH v3 2/8] ShellPkg/AcpiView: Declutter error counters'
I feel accessor methods offer a better design and should be retained.

Other patches in the series need a bit of rework to follow coding conventions etc.

This patch series has too many changes to the parsers. I request to put this patch series on hold as we have other patches that need to go in on priority. e.g. loop detection in PPTT table.

Since Tomas is no longer with Arm, someone from Arm will pick up repost the reworked series.

Regards,

Sami Mujawar

-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Gao, Zhichao via groups.io
Sent: 31 July 2020 01:43 AM
To: devel@edk2.groups.io; tomas@nuviainc.com
Subject: Re: [edk2-devel] acpiview error handling patches

I am  busy at other works recent weeks. I plan to review the patch in next two weeks. Hope it is acceptable for you.

Thanks,
Zhichao

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Tomas
> Pilar
> (tpilar)
> Sent: Wednesday, July 29, 2020 7:23 PM
> To: Gao; Gao, Zhichao <zhichao.gao@intel.com>; devel@edk2.groups.io
> Subject: Re: [edk2-devel] acpiview error handling patches
>
> (change of email)
>
> Hi Zhichao,
>
> I've amended the patches and respun a v3 version. Any chance you could
> have a look to see if I've fixed the issues correctly?
>
> Cheers,
> Tom
>
>




IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2020-08-11 13:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 10:11 acpiview error handling patches Tomas Pilar (tpilar)
2020-07-08  2:30 ` Gao, Zhichao
2020-07-29 11:22   ` [edk2-devel] " Tomas Pilar (tpilar)
2020-07-31  0:43     ` Gao, Zhichao
2020-08-11 13:45       ` Sami Mujawar [this message]
2020-08-12  0:41         ` Gao, Zhichao
2020-08-12 16:22           ` Sami Mujawar

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=DB7PR08MB309778463494E31D8CE2B94784450@DB7PR08MB3097.eurprd08.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