From: Thierry Herbelot <thierry.herbelot@6wind.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [dpdk-dev] Typos in Arm xconfig files
Date: Mon, 1 Feb 2021 18:05:53 +0100 [thread overview]
Message-ID: <7a4b591b-5e32-a3f8-a8ff-59a636217814@6wind.com> (raw)
Hello,
There is an inconsistency in the name of variables:
most xconfig files use 'implementer_id'
two still use 'implementor_id'
Regards
Thierry
--
Thierry Herbelot
Senior Software Engineer
Tel: +33 1 39 30 92 61
http://www.6wind.com/
Follow us:
https://www.linkedin.com/company/6wind/
https://twitter.com/6WINDsoftware
https://www.youtube.com/user/6windsoftware
next reply other threads:[~2021-02-01 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 17:05 Thierry Herbelot [this message]
2021-02-01 22:41 ` [dpdk-dev] [PATCH] config/arm: fix typo in meson config Ferruh Yigit
2021-02-01 23:22 ` Honnappa Nagarahalli
2021-02-02 2:19 ` Ruifeng Wang
2021-02-02 8:08 ` Ferruh Yigit
2021-02-02 7:12 ` Juraj Linkeš
2021-02-02 8:35 ` [dpdk-dev] [PATCH v2] config/arm: fix variable name Ferruh Yigit
2021-02-02 9:22 ` 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=7a4b591b-5e32-a3f8-a8ff-59a636217814@6wind.com \
--to=thierry.herbelot@6wind.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
/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).