From: Stephen Hemminger <stephen@networkplumber.org>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] coding style question - c99 comments
Date: Thu, 23 Jan 2020 08:15:18 -0800 [thread overview]
Message-ID: <20200123081518.4c836e60@hermes.lan> (raw)
In-Reply-To: <CADyeNEDOtD+4wZGX42FgZBLPM0yJ_tSVh6e0Or+J2o7zfgK9Dw@mail.gmail.com>
On Thu, 23 Jan 2020 11:05:58 -0500
Lance Richardson <lance.richardson@broadcom.com> wrote:
> The DPDK Coding Style document doesn't mention the use of c99 comments
> using '//' as a comment delimiter, but it does say that traditional
> '/* */' comment
> delimiters should be used and therefore seems to imply that c99-style comments
> are not allowed.
>
> Is this correct?
>
> Lance
Don't use c99 comments.
These will get flagged by checkpatch
next prev parent reply other threads:[~2020-01-23 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 16:05 [dpdk-dev] coding style question - c99 comments Lance Richardson
2020-01-23 16:15 ` Stephen Hemminger [this message]
2020-01-23 16:43 ` Lance Richardson
2020-01-24 17:07 ` Ferruh Yigit
2020-01-24 21:37 ` Lance Richardson
2020-02-15 17:09 ` [dpdk-dev] [PATCH v2] devtools: check c99 comment use in checkpatches.sh Lance Richardson
2020-02-22 19:52 ` Thomas Monjalon
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=20200123081518.4c836e60@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=lance.richardson@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.