From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Wang, Jian J" <jian.j.wang@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH 0/4] Coding style clean-up
Date: Tue, 26 Dec 2017 16:47:54 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5A7DF26A0@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <20171225010659.13428-1-jian.j.wang@intel.com>
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 specification. In this case
these fields are all listed in a structure in
the Intel 64 and IA-32 Architectures Software
Development Manual, Section 7.2.1, Figure 7-2
using upper case register names.
Thanks,
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org]
> On Behalf Of Jian J Wang
> Sent: Sunday, December 24, 2017 5:07 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH 0/4] Coding style clean-up
>
> 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 new structure field
> names
>
> MdeModulePkg/Core/DxeIplPeim/X64/VirtualMemory.c | 5
> ++
> MdePkg/Include/Library/BaseLib.h | 72
> +++++++++++-----------
> .../Ia32/ArchExceptionHandler.c | 24
> ++++----
> .../X64/ArchExceptionHandler.c | 6
> +-
> UefiCpuPkg/Library/MpInitLib/MpLib.c | 2
> +-
> UefiCpuPkg/UefiCpuPkg.uni | 16
> ++++-
> 6 files changed, 71 insertions(+), 54 deletions(-)
>
> --
> 2.15.1.windows.2
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-12-26 16:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 1:06 [PATCH 0/4] Coding style clean-up Jian J Wang
2017-12-25 1:06 ` [PATCH 1/4] MdePkg/BaseLib.h: " Jian J Wang
2017-12-25 1:51 ` Bi, Dandan
2017-12-25 2:23 ` Wang, Jian J
2017-12-25 1:06 ` [PATCH 2/4] MdeModulePkg/Core: " Jian J Wang
2017-12-25 1:19 ` Zeng, Star
2017-12-25 2:01 ` Bi, Dandan
2017-12-25 1:06 ` [PATCH 3/4] UefiCpuPkg/UefiCpuPkg.uni: Add missing string definition for new PCDs Jian J Wang
2017-12-25 1:58 ` Bi, Dandan
2017-12-25 2:28 ` Wang, Jian J
2017-12-25 1:06 ` [PATCH 4/4] UefiCpuPkg: Update code to use new structure field names Jian J Wang
2017-12-25 2:01 ` Bi, Dandan
2017-12-26 16:47 ` Kinney, Michael D [this message]
2017-12-27 0:40 ` [PATCH 0/4] Coding style clean-up Wang, Jian J
2017-12-27 9:29 ` Gao, Liming
2017-12-27 16:35 ` Kinney, Michael D
2017-12-28 0:27 ` Wang, Jian J
2017-12-28 0:37 ` Kinney, Michael D
2017-12-28 0:53 ` Wang, Jian J
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=E92EE9817A31E24EB0585FDF735412F5A7DF26A0@ORSMSX113.amr.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