From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ed Czeck <ed.czeck@atomicrules.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] checkpatch question -- CamelCase versus PRIu32
Date: Tue, 21 Mar 2017 10:01:11 +0000 [thread overview]
Message-ID: <4d56e27a-ae3c-1205-2e48-26d072575eb0@intel.com> (raw)
In-Reply-To: <CALZ3Gui5HKSCEXAA9VyHoHN2LsUL5dArDppDTwuXwfSPwFfLiw@mail.gmail.com>
On 3/20/2017 3:58 PM, Ed Czeck wrote:
> Hi All,
> I have a small number checkpatch.sh messages in the pattern below. The
> message is a conflict between the definition of PRIu32 in the system header
> files and the DPDK checkpatch setup.
>
> CHECK:CAMELCASE: Avoid CamelCase: <PRIu32>
> #866: FILE: drivers/net/ark/ark_debug.h:41:
> +#define ARK_SU32 "\n\t%-20s %'20" PRIu32
>
> Is there a preferred way to resolve this?
Not I am aware of,
overall camel case syntax is not preferred in DPDK, and you can ignore
warnings for PRIu32, PRIu64 ..
>
> Thanks
> Ed
>
prev parent reply other threads:[~2017-03-21 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 15:58 Ed Czeck
2017-03-21 10:01 ` Ferruh Yigit [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=4d56e27a-ae3c-1205-2e48-26d072575eb0@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.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).