public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chang, Abner" <abner.chang@amd.com>
To: "Ni, Ray" <ray.ni@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [tianocore-docs][PATCH V2 2/2] edk II C Coding Standard: Updates 4.2 and 4.3 sections
Date: Wed, 19 Oct 2022 04:17:56 +0000	[thread overview]
Message-ID: <MN2PR12MB3966974D5109E5FB3B64C8DFEA2B9@MN2PR12MB3966.namprd12.prod.outlook.com> (raw)
In-Reply-To: <MWHPR11MB16317468CC10E4513F186FD88C2B9@MWHPR11MB1631.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3034 bytes --]

[AMD Official Use Only - General]

Thanks! I will send out the V3 for the update. Will work on the spec publication with Mike.

Abner


From: Ni, Ray <ray.ni@intel.com>
Sent: Wednesday, October 19, 2022 11:34 AM
To: Chang, Abner <Abner.Chang@amd.com>; devel@edk2.groups.io
Subject: RE: [edk2-devel] [tianocore-docs][PATCH V2 2/2] edk II C Coding Standard: Updates 4.2 and 4.3 sections

Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.

Oh I see!

Reviewed-by: Ray Ni <ray.ni@intrel.com<mailto:ray.ni@intrel.com>>

From: Chang, Abner <Abner.Chang@amd.com<mailto:Abner.Chang@amd.com>>
Sent: Tuesday, October 18, 2022 5:50 PM
To: Ni, Ray <ray.ni@intel.com<mailto:ray.ni@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: RE: [edk2-devel] [tianocore-docs][PATCH V2 2/2] edk II C Coding Standard: Updates 4.2 and 4.3 sections


[AMD Official Use Only - General]

Hi Ray,

<CpuArch>][<Vendor>]<FileName>.*

The simple <FileName> naming rule was already  defined in the 4.3.1 to 4.3.4 sections. We are not intending for defining the file naming style. This section is mainly for the format of attaching <CpuArch> and <Vendor> to the filename.
For example, how do we add AMD to SmmCpuFeaturesLib? Is "Amd"SmmCpuFeaturesLib or SmmCpuFeaturesLib"Amd"? This is what we would like to define for the processor archs and vendors.
My opinion is we can just leave the file format naming as it was defined in this spec.

Or how about if we say "Refer to 4.3.1 to 4.3.4 sections for the file naming format" for <FileNmae> in below?

[<CpuArch>][<Vendor>]<FileName>.*

   <CpuArch>   OPTIONAL   The <CpuArch> is represented with a BNF,
                          <arch> ::='Ia32' | 'X64' | 'Arm' | 'AArch64' | 'RiscV64' |
                                    'LoongArch64' | 'Ebc'
                          <CpuArch> ::= <arch>[<arch>]*

                          Example: Ia32X64Arm or RiscV64LoongArch64
   <Vendor>    OPTIONAL   *
   <FileName>  REQUIRED   Refer to 4.3.1 to 4.3.4 sections for the file
                          Naming format.

Thanks
Abner

From: Ni, Ray <ray.ni@intel.com<mailto:ray.ni@intel.com>>
Sent: Tuesday, October 18, 2022 2:02 PM
To: Chang; Chang, Abner <Abner.Chang@amd.com<mailto:Abner.Chang@amd.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: Re: [edk2-devel] [tianocore-docs][PATCH V2 2/2] edk II C Coding Standard: Updates 4.2 and 4.3 sections

Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.


All look good to me. Thanks for addressing my comments regarding simplifying the rules.

Except for one minor comment: I still don't think we need to define rules for source file names (4.3.5.4 EDK II source files within a Library/Module instance). And the rule "[][].*" doesn't specify what could be. That leads to allowing any style of the file name.

[-- Attachment #2: Type: text/html, Size: 11659 bytes --]

  reply	other threads:[~2022-10-19  4:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15 11:47 [tianocore-docs][PATCH V2 2/2] edk II C Coding Standard: Updates 4.2 and 4.3 sections Chang, Abner
2022-10-18  6:01 ` [edk2-devel] " Ni, Ray
2022-10-18  9:50   ` Chang, Abner
2022-10-19  1:31     ` Chang, Abner
2022-10-19  3:34     ` Ni, Ray
2022-10-19  4:17       ` Chang, Abner [this message]
2022-10-18 13:33 ` Sunil V L
2022-10-18 15:23   ` Chang, Abner
2022-10-19  2:24 ` Attar, AbdulLateef (Abdul Lateef)

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=MN2PR12MB3966974D5109E5FB3B64C8DFEA2B9@MN2PR12MB3966.namprd12.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