From: bugzilla@dpdk.org
To: dts@dpdk.org
Subject: [Bug 966] Document the coding standards for DTS
Date: Tue, 22 Mar 2022 12:47:00 +0000 [thread overview]
Message-ID: <bug-966-433@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=966
Bug ID: 966
Summary: Document the coding standards for DTS
Product: DTS
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: framework
Assignee: dts@dpdk.org
Reporter: juraj.linkes@pantheon.tech
Target Milestone: ---
Document coding standards for DTS. Establish automated tools to enforce the
coding standards.
The coding standard must address how the changes that impact CI systems (ex:
changes to config files, changes to test case output format, changes to json
objects in reports) should be handled (for ex: such changes should follow a
deprecation procedure).
The standard should also cover restricted use of “eval”.
The coding standard must establish static analysis tools.
The work in progress is captured here:
https://docs.google.com/document/d/1G7_AEA-4MAd88bxjfP-IOcIy_6mnrMz3HCsUI8e-NN4/edit?pli=1#
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-03-22 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-all 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=bug-966-433@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dts@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).