From: "Dong, Eric" <eric.dong@intel.com>
To: Laszlo Ersek <lersek@redhat.com>, "Ni, Ray" <ray.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch 2/2] UefiCpuPkg/RegisterCpuFeaturesLib: Avoid AP calls PeiService.
Date: Tue, 8 Jan 2019 05:32:31 +0000 [thread overview]
Message-ID: <ED077930C258884BBCB450DB737E662259D866D5@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <3ea78f2e-0e77-3ebc-81ac-84df978de197@redhat.com>
Hi Laszlo,
Thanks for your detail check, sorry for this mistake. I will send V4 changes and only Cc Ray.
I based on do the minimal change rule to create v2 change, so some code may seems ugly.
I based on do the clean code rule to create V3 change, so the change may seems big.
Thanks,
Eric
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Tuesday, January 8, 2019 3:18 AM
> To: Ni, Ray <ray.ni@intel.com>; Dong, Eric <eric.dong@intel.com>; edk2-
> devel@lists.01.org
> Subject: Re: [Patch 2/2] UefiCpuPkg/RegisterCpuFeaturesLib: Avoid AP calls
> PeiService.
>
> On 01/07/19 09:24, Ni, Ray wrote:
> > 1.
> > How about defining a union for MpService.
> > typedef union {
> > EFI_MP_SERVICES_PROTOCOL *Protocol;
> > EFI_PEI_MP_SERVICES_PPI *Ppi;
> > } MP_SERVICES;
> > So a new field as below can be added here:
> >
> > MP_SERVICES MpService;
> >
> > GetMpService() can be also changed to return MP_SERVICES;
> >
> > 2. Please update the copyright year to 2019.
>
> - I wasn't CC'd on the cover letter, and the patches themselves don't include
> any version numbers, so it's hard to tell what version this is.
>
> - Upon examining my list folder, in addition to my inbox, the cover letter
> seems to be "[edk2] [Patch v2 0/2] Avoid AP calls PeiServices table." -- at
> <https://lists.01.org/pipermail/edk2-devel/2019-January/034675.html>.
>
> That's incorrect; this is version 3 actually. V1 was at
> <https://lists.01.org/pipermail/edk2-devel/2018-December/034262.html>,
> and the actual v2 was at
> <https://lists.01.org/pipermail/edk2-devel/2018-December/034440.html>.
>
> - As I stated under v2, at
> <https://lists.01.org/pipermail/edk2-devel/2018-December/034493.html>,
> I'll defer to Ray on v3.
>
> Thanks,
> Laszlo
prev parent reply other threads:[~2019-01-08 5:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 1:05 [Patch v2 0/2] Avoid AP calls PeiServices table Eric Dong
2019-01-07 1:05 ` [Patch v2 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: Enhance debug message Eric Dong
2019-01-07 7:53 ` Ni, Ruiyu
2019-01-07 1:05 ` [Patch 2/2] UefiCpuPkg/RegisterCpuFeaturesLib: Avoid AP calls PeiService Eric Dong
[not found] ` <734D49CCEBEEF84792F5B80ED585239D5BFA53EB@SHSMSX103.ccr.corp.intel.com>
2019-01-07 19:17 ` Laszlo Ersek
2019-01-08 5:32 ` Dong, Eric [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=ED077930C258884BBCB450DB737E662259D866D5@shsmsx102.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