From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PKTGEN] OK to reindent the pktgen (mix of tabs and spaces, etc.)?
Date: Sun, 3 Jan 2016 23:35:59 +0000 [thread overview]
Message-ID: <20160103233559.GA27869@sivlogin002.ir.intel.com> (raw)
In-Reply-To: <674FEFDF-70BD-4C02-947B-10C9F9FC862C@intel.com>
On Sun, Jan 03, 2016 at 05:09:16PM +0000, Wiles, Keith wrote:
<snip>
> A bigger question is what is the coding style of DPDK and where is it documented? I looked in the docs/web site and did not find any coding style suggestions. Maybe I missed it someplace.
There is one in:
http://dpdk.org/doc/guides/contributing/coding_style.html
Regards,
ferruh
next prev parent reply other threads:[~2016-01-03 23:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 17:09 Wiles, Keith
2016-01-03 22:07 ` Matthew Hall
2016-01-03 23:06 ` Stephen Hemminger
2016-01-04 2:35 ` Wiles, Keith
2016-01-03 23:35 ` Ferruh Yigit [this message]
2016-01-04 0:15 ` Wiles, Keith
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=20160103233559.GA27869@sivlogin002.ir.intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
/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).