From: David Marchand <david.marchand@redhat.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org
Subject: Re: If feeling bored
Date: Tue, 12 Sep 2023 18:50:02 +0100 [thread overview]
Message-ID: <CAJFAV8yTQHTA0Z-O5iA6LPk04Csu8guw98vKjdU5z5MOcxkU9A@mail.gmail.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D87BA7@smartserver.smartshare.dk>
On Tue, Sep 12, 2023 at 5:46 PM Morten Brørup <mb@smartsharesystems.com> wrote:
> RTE_LIBRTE_xxx seems redundant. There are still a bunch of those in DPDK, which could be replaced by RTE_xxx.
>
> Cleaning up this will probably break the API.
If we exclude config/ doc/ and any rte_.*.h header, we should be good?
$ for pattern in $(git grep -o 'RTE_LIBRTE_[A-Z0-9_]*' ':^**/rte**.h'
':^config/' ':^doc/'); do file=${pattern%%:*}; symbol=${pattern##*:};
! git grep -wq $symbol '**/rte**.h' config/ doc/ || continue; sed -i
-e "s/$symbol/${symbol##RTE_LIB}/g" $file; done
$ git diff --stat
...
135 files changed, 437 insertions(+), 437 deletions(-)
$ ninja -C build
...
There are still some exposed defines but it is a first move forward.
$ git grep RTE_LIBRTE_ | wc
306 1010 22337
--
David Marchand
next prev parent reply other threads:[~2023-09-12 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 16:46 Morten Brørup
2023-09-12 17:50 ` David Marchand [this message]
2023-09-12 22:21 ` Morten Brørup
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=CAJFAV8yTQHTA0Z-O5iA6LPk04Csu8guw98vKjdU5z5MOcxkU9A@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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 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).