DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lance Richardson <lance.richardson@broadcom.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] coding style question - c99 comments
Date: Thu, 23 Jan 2020 11:43:47 -0500	[thread overview]
Message-ID: <CADyeNEDqFakWx=q_=tvCwsxtsEBE8thEMoPoXTZ5x-BVXucHqQ@mail.gmail.com> (raw)
In-Reply-To: <20200123081518.4c836e60@hermes.lan>

On Thu, Jan 23, 2020 at 11:15 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> 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

Hi Stephen,

Actually, the reason I was asking was they aren't being flagged by checkpatch.

It seems checkpatch.pl now has this:
my $allow_c99_comments = 1; # Can be overridden by --ignore
C99_COMMENT_TOLERANCE

If c99 comments are should not be allowed, it looks like
C99_COMMENT_TOLERANCE should
be added to the list of checkers to ignore in checkpatches.sh. I was
thinking of rolling a patch,
but wanted to first confirm that they are actually not allowed.

Thanks,

   Lance

  reply	other threads:[~2020-01-23 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 16:05 Lance Richardson
2020-01-23 16:15 ` Stephen Hemminger
2020-01-23 16:43   ` Lance Richardson [this message]
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='CADyeNEDqFakWx=q_=tvCwsxtsEBE8thEMoPoXTZ5x-BVXucHqQ@mail.gmail.com' \
    --to=lance.richardson@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).