From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "Chang, Abner" <Abner.Chang@amd.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
Michael Kubacki <mikuback@linux.microsoft.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Wee, Sing" <sing.wee@microsoft.com>,
Rebecca Cran <rebecca@quicinc.com>,
"lersek@redhat.com" <lersek@redhat.com>,
"heyi.guo@linaro.org" <heyi.guo@linaro.org>
Subject: Re: [edk2-devel] [edk2-CCodingStandardsSpecification] Create release/2.30 branch
Date: Mon, 7 Nov 2022 17:07:03 +0000 [thread overview]
Message-ID: <CO1PR11MB49299075BE4285678DD6A84CD23C9@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MN2PR12MB396632C651BA7B86B8C14FFCEA3C9@MN2PR12MB3966.namprd12.prod.outlook.com>
Hi Abner,
Thanks for the review. I agree we should try to get a few more of these resolved for Version 2.3.
+Michael Kubacki for Uncrustify configuration settings discussion on the column width
and args per line in function call topics. We need to know what the current Uncrustify
configuration settings for these 2 topics. It would be better of the spec and the
Uncrustify settings were aligned and for any changes going forward they are made to the
spec and Uncrustify settings at the same time.
Details of these 2 topics are as follows:
* TianoCore BZ links:
https://bugzilla.tianocore.org/show_bug.cgi?id=713 - Update EDK II C Coding standard to state a stronger preference for 80 column line widths
https://bugzilla.tianocore.org/show_bug.cgi?id=714 - Update EDK II C Coding Standards to allow multiple arguments per line in a function call
* The patch emails and discussions are in groups.io:
https://edk2.groups.io/g/devel/message/13204
https://edk2.groups.io/g/devel/message/13205
Leif provide a Reviewed-by: https://edk2.groups.io/g/devel/message/13228
https://edk2.groups.io/g/devel/message/13206
There is a good discussion of this change with no Rb.
* The links to the formatted versions of the reviews are no longer working,
but they can be view on GitHub in the branch Laszlo provided and select the
"Display the rich diff" view of the markdown changes:
https://github.com/lersek/edk2-CCodingStandardsSpecification/commit/2c5534a24b15616fdaa02478858ed1d8908dc653
https://github.com/lersek/edk2-CCodingStandardsSpecification/commit/e3797dc48316052005cefa26246ab2fd32641881
Best regards,
Mike
> -----Original Message-----
> From: Chang, Abner <Abner.Chang@amd.com>
> Sent: Monday, November 7, 2022 6:18 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2.groups.io
> Cc: Wee, Sing <sing.wee@microsoft.com>; Rebecca Cran <rebecca@quicinc.com>; lersek@redhat.com; heyi.guo@linaro.org
> Subject: RE: [edk2-devel] [edk2-CCodingStandardsSpecification] Create release/2.30 branch
>
> [AMD Official Use Only - General]
>
> Hi Mike,
> You probably missed this email. I checked the below C coding standard spec related BZ and had some comments in line below.
>
> > -----Original Message-----
> > From: Chang, Abner
> > Sent: Saturday, October 29, 2022 11:33 AM
> > To: Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2.groups.io
> > Subject: RE: [edk2-devel] [edk2-CCodingStandardsSpecification] Create
> > release/2.30 branch
> >
> > [AMD Official Use Only - General]
> >
> > Hi Mike,
> > Below are the tickets pulled out from BZ, is there any one you think is not
> > necessary now?
> > Abner
> >
> > 713 EDK2 Document michael.d.kinney@intel.com CONF ---
> > Update EDK II C Coding standard to state a stronger preference for 80
> > column line widths 2021-07-27
> Seems no conclusion from the discussion in BZ.
>
> > 1766 EDK2 Document michael.d.kinney@intel.com CONF ---
> > Remove use of STATIC macros from EDK II C Coding Standard
> > Specification 2020-12-09
> No conclusion yet.
>
> > 1698 EDK2 Document michael.d.kinney@intel.com CONF ---
> > Spurious rule about comment style in CCS 6.2.3 2021-07-27
> Had we addressed this issue on the coding standard spec yet? If not, we can fix this in the version 2.3.
>
> > 714 EDK2 Document michael.d.kinney@intel.com CONF ---
> > Update EDK II C Coding Standards to allow multiple arguments per
> > line in a function call 2021-07-27
> Have these patches been reviewed?
> [edk2] [edk2-CCodingStandardsSpecification PATCH 0/2] improvements related to line wrapping
> [edk2] [edk2-CCodingStandardsSpecification PATCH 1/2] Source Files / General Rules: limit line lengths to 80 columns
> [edk2] [edk2-CCodingStandardsSpecification PATCH 2/2] Source Files / Spacing / Multi-line func. calls: allow condensed arguments
>
> http://mid.mail-archive.com/20170811164851.9466-1-lersek@redhat.com
> http://mid.mail-archive.com/20170811164851.9466-2-lersek@redhat.com
> http://mid.mail-archive.com/20170811164851.9466-3-lersek@redhat.com
>
> > 2664 EDK2 Document michael.d.kinney@intel.com CONF ---
> > Discrepancies/inconsistencies in coding standards, style and
> > examples 2021-10-02
> I think we can fix the above inconsistent issues in the version 2.3 release.
>
> Thanks
> Abner
>
> >
> > > -----Original Message-----
> > > From: Kinney, Michael D <michael.d.kinney@intel.com>
> > > Sent: Friday, October 28, 2022 11:22 PM
> > > To: devel@edk2.groups.io; Chang, Abner <Abner.Chang@amd.com>;
> > Kinney,
> > > Michael D <michael.d.kinney@intel.com>
> > > Subject: RE: [edk2-devel] [edk2-CCodingStandardsSpecification] Create
> > > release/2.30 branch
> > >
> > > Caution: This message originated from an External Source. Use proper
> > > caution when opening attachments, clicking links, or responding.
> > >
> > >
> > > Hi Abner,
> > >
> > > Have you reviewed the open BZs against the EDK II C Coding Standard.
> > >
> > > Are there any other issues that are considered important to fix before
> > > making a new official release?
> > >
> > > Thanks,
> > >
> > > Mike
> > >
> > > > -----Original Message-----
> > > > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of
> > > > Chang, Abner via groups.io
> > > > Sent: Thursday, October 27, 2022 9:54 AM
> > > > To: devel@edk2.groups.io
> > > > Cc: Abner Chang <abner.chang@amd.com>
> > > > Subject: [edk2-devel] [edk2-CCodingStandardsSpecification] Create
> > > > release/2.30 branch
> > > >
> > > > Contributed-under: TianoCore Contribution Agreement 1.1
> > > > Signed-off-by: Abner Chang <abner.chang@amd.com>
> > > > ---
> > > > book.json | 3 +--
> > > > 1 file changed, 1 insertion(+), 2 deletions(-)
> > > >
> > > > diff --git a/book.json b/book.json
> > > > index d112b26..1fdd570 100644
> > > > --- a/book.json
> > > > +++ b/book.json
> > > > @@ -1,8 +1,7 @@
> > > > {
> > > >
> > > > "variables" : {
> > > >
> > > > - "draft" : "yes",
> > > >
> > > > "title" : "EDK II C Coding Standards Specification",
> > > >
> > > > - "version" : "Revision 2.2"
> > > >
> > > > + "version" : "Revision 2.3"
> > > >
> > > > },
> > > >
> > > > "plugins": ["puml-aleung"],
> > > >
> > > > "pluginsConfig": {}
> > > >
> > > > --
> > > > 2.37.1.windows.1
> > > >
> > > >
> > > >
> > > >
> > > >
next prev parent reply other threads:[~2022-11-07 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 16:54 [edk2-CCodingStandardsSpecification] Create release/2.30 branch Chang, Abner
2022-10-28 15:22 ` [edk2-devel] " Michael D Kinney
2022-10-29 3:33 ` Chang, Abner
2022-11-07 14:18 ` Chang, Abner
2022-11-07 17:07 ` Michael D Kinney [this message]
2022-11-13 1:37 ` Chang, Abner
2022-11-13 2:01 ` Michael D Kinney
2022-11-13 8:53 ` Chang, Abner
2022-11-13 17:33 ` Michael D Kinney
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=CO1PR11MB49299075BE4285678DD6A84CD23C9@CO1PR11MB4929.namprd11.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