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 14:26:14 +0200 [thread overview]
Message-ID: <CAJFAV8wErAC53Y4MBd=ERwmO4MpL2vEBrE6TObwr71AeY+qYcA@mail.gmail.com> (raw)
In-Reply-To: <YqcJWcZkpwDiXkdb@bricha3-MOBL.ger.corp.intel.com>
On Mon, Jun 13, 2022 at 11:54 AM Bruce Richardson
<bruce.richardson@intel.com> wrote:
> On Thu, Dec 16, 2021 at 11:14:30AM +0000, Bruce Richardson wrote:
> > Rather than explicitly clearing any setting of undefined values in our
> > rte_config.h file, it's better to instead just add a comment that the
> > value is not set. Using a comment allows the user to set the value using
> > CFLAGS or similar mechanism without the config file clearing the value
> > again.
> >
> > The text used "<VALUE> is not set" is modelled after the kernel approach
> > of doing the same thing.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
> >
> > Although DPDK coding convention forbids use of "//" for comments, using
> > regular C comment style makes the config settings less clear, as they can
> > be confused with regular comments in the file. Using "//" makes them stand
> > out better, so I prefer it. However, if others feel strongly, they can be
> > changed to standard.
> >
> > Note: this is a resubmission of patch [1] which was part of a rejected
> > series. However, the reasons for rejection - values in config being out
> > of sync with those used for building apps - are less relevant for
> > many, if not all, of these setting, so I believe the benefits for
> > testing outweigh the potential downsides. If any setting is likely
> > problematic, I can keep the explicit undef for that case in a new patch
> > version.
> >
> > [1] http://patches.dpdk.org/project/dpdk/patch/20200903144942.671870-2-bruce.richardson@intel.com/
> > ---
>
> Ping for review or feedback for this patch. I'd like to see it move forward
> into a DPDK release if possible.
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.
--
David Marchand
next prev parent reply other threads:[~2022-06-13 12:26 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 [this message]
2022-06-13 12:37 ` Bruce Richardson
2022-06-13 14:20 ` David Marchand
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='CAJFAV8wErAC53Y4MBd=ERwmO4MpL2vEBrE6TObwr71AeY+qYcA@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).