DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, "Dong, JunX" <junx.dong@intel.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Thomas Monjalon" <thomas@monjalon.net>
Subject: Re: [PATCH] config: remove explicit undef of unset values
Date: Mon, 13 Jun 2022 16:20:04 +0200	[thread overview]
Message-ID: <CAJFAV8zYeVaCwKXvtN4yvjpOchpKy6U9_TuY4+C9M=4yu4y50A@mail.gmail.com> (raw)
In-Reply-To: <YqcvfQ4CBCjrT6aJ@bricha3-MOBL.ger.corp.intel.com>

On Mon, Jun 13, 2022 at 2:37 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
> > I'd like a check like (below), to avoid new additions:
> >
> > diff --git a/devtools/checkpatches.sh b/devtools/checkpatches.sh
> > index 34a2e43845..8dae47165e 100755
> > --- a/devtools/checkpatches.sh
> > +++ b/devtools/checkpatches.sh
> > @@ -158,6 +158,14 @@ check_forbidden_additions() { # <patch>
> >                 -f $(dirname $(readlink -f $0))/check-forbidden-tokens.awk \
> >                 "$1" || res=1
> >
> > +       # '// XXX is not set' must be preferred over '#undef XXX'
> > +       awk -v FOLDERS='config/rte_config.h' \
> > +               -v EXPRESSIONS='#undef' \
> > +               -v RET_ON_FAIL=1 \
> > +               -v MESSAGE='Using "#undef XXX", prefer "// XXX is not set"' \
> > +               -f $(dirname $(readlink -f $0))/check-forbidden-tokens.awk \
> > +               "$1" || res=1
> > +
> >         return $res
> >  }
> >
> > Otherwise, the change lgtm.
> >
> Good idea. Do you want me to add your check above as a patch to this to
> make a two-patch set for v2?

If you are fine with the check, I don't mind it is part of this simple patch.
I can do it when applying if you are okay with it.


-- 
David Marchand


  reply	other threads:[~2022-06-13 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 11:14 Bruce Richardson
2022-06-13  9:54 ` Bruce Richardson
2022-06-13 10:01   ` Morten Brørup
2022-06-13 12:26   ` David Marchand
2022-06-13 12:37     ` Bruce Richardson
2022-06-13 14:20       ` David Marchand [this message]
2022-06-13 14:48         ` Bruce Richardson
2022-06-13 14:46   ` Tyler Retzlaff
2022-06-15  7:14 ` David Marchand

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='CAJFAV8zYeVaCwKXvtN4yvjpOchpKy6U9_TuY4+C9M=4yu4y50A@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=junx.dong@intel.com \
    --cc=mb@smartsharesystems.com \
    --cc=thomas@monjalon.net \
    /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).