DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] checkpatch question -- CamelCase versus PRIu32
@ 2017-03-20 15:58 Ed Czeck
  2017-03-21 10:01 ` Ferruh Yigit
  0 siblings, 1 reply; 2+ messages in thread
From: Ed Czeck @ 2017-03-20 15:58 UTC (permalink / raw)
  To: dev

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?

Thanks
Ed

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-dev] checkpatch question -- CamelCase versus PRIu32
  2017-03-20 15:58 [dpdk-dev] checkpatch question -- CamelCase versus PRIu32 Ed Czeck
@ 2017-03-21 10:01 ` Ferruh Yigit
  0 siblings, 0 replies; 2+ messages in thread
From: Ferruh Yigit @ 2017-03-21 10:01 UTC (permalink / raw)
  To: Ed Czeck, dev

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
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-03-21 10:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-20 15:58 [dpdk-dev] checkpatch question -- CamelCase versus PRIu32 Ed Czeck
2017-03-21 10:01 ` Ferruh Yigit

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).