From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] Coding standards
Date: Tue, 19 May 2015 11:23:27 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2F29EA4@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1431531022-29697-1-git-send-email-bruce.richardson@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Wednesday, May 13, 2015 4:30 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] Coding standards
>
> When reviewing please remember: This document is designed to put in
> writing the
> *existing* code guidelines for DPDK that are implied by the existing code.
> It is *not* intended that we should have to make any across-the-board code
> changes as the basis of this document until after it has been merged in -
> so if you are suggesting something that is not already prevalent in DPDK
> code, please hold that thought until after we get the existing style
> locked down! :-)
I think that the above paragraph is the important part. This document lays out the coding standards as they were (or should have been) applied to the original DPDK code. This document can be viewed as the baseline coding standards. Changes or improvements can be submitted as patches and debated on the ML.
Acked-by: John McNamara <john.mcnamara@intel.com>
prev parent reply other threads:[~2015-05-19 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 15:30 Bruce Richardson
2015-05-13 15:30 ` [dpdk-dev] [PATCH] doc: add coding standards documentation Bruce Richardson
2015-06-02 12:59 ` Thomas Monjalon
2015-06-03 10:43 ` Bruce Richardson
2015-06-03 13:58 ` [dpdk-dev] [PATCH v2] " Bruce Richardson
2015-06-03 17:35 ` Thomas Monjalon
2015-06-04 9:33 ` Bruce Richardson
2015-06-04 9:49 ` Thomas Monjalon
2015-06-04 13:36 ` Bruce Richardson
2015-05-19 11:23 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE2F29EA4@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).