ntel.com>; edk2-devel@lists.01.org; Kinney,
> Michael D <michael.d.kin...@intel.com>
> Subject: RE: [edk2] [PATCH 0/4] Coding style clean-up
>
> Jian,
>
> I think . is the correct way to list
> this type of exception. Otherwise we can miss incorrect
> use of that fi
>;
> edk2-devel@lists.01.org
> Subject: RE: [edk2] [PATCH 0/4] Coding style clean-up
>
> Current ECC use . in exception
> list to exclude those special
> field name spec defined. Whenever there's a new
> structure introduced with those field
> names, which have been added to e
sts.01.org; Kinney,
> Michael D <michael.d.kin...@intel.com>
> Subject: RE: [edk2] [PATCH 0/4] Coding style clean-up
>
> Yes. Please revert.
>
> I am not sure I understand the ECC tool update you are suggesting.
> Can you provide more details?
>
> Mike
>
-
> de...@lists.01.org
> Subject: RE: [edk2] [PATCH 0/4] Coding style clean-up
>
> Hi Mike,
>
> Since this patch has been checked in trunk, do you think
> it should be reverted?
> In addition, instead of using exception list for the ECC
> tool, I think it'd be better
>
>To: Kinney, Michael D <michael.d.kin...@intel.com>; edk2-
>de...@lists.01.org
>Subject: Re: [edk2] [PATCH 0/4] Coding style clean-up
>
>Hi Mike,
>
>Since this patch has been checked in trunk, do you think it should be reverted?
>In addition, instead of using exception list
hael D <michael.d.kin...@intel.com>
> Subject: RE: [edk2] [PATCH 0/4] Coding style clean-up
>
> Jian,
>
> I do not think this change should be made.
>
> One of the exceptions for not following the
> EDK II code style is if the field names are
> defined in a public spec
This patch series are meant for cleaning up code according to coding style
requirements.
Jian J Wang (4):
MdePkg/BaseLib.h: Coding style clean-up
MdeModulePkg/Core: Coding style clean-up
UefiCpuPkg/UefiCpuPkg.uni: Add missing string definition for new PCDs
UefiCpuPkg: Update code to use
7 matches
Mail list logo
