From: Liron Himi <lironh@marvell.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
Liron Himi <lironh@marvell.com>
Subject: [dpdk-dev] checkpatch failing on map change
Date: Tue, 17 Dec 2019 07:36:20 +0000 [thread overview]
Message-ID: <MN2PR18MB23989F4988B3B758983DA5C9C6500@MN2PR18MB2398.namprd18.prod.outlook.com> (raw)
Hi,
One of our drivers is using the rte_cfgfile and meson is failing on 'rte_cfgfile_section_num_entries_by_index' which is undefined.
After a few debug cycles, I found out that this function is missing from the .map file.
So I added it and created a patch but checkpatch is failing with
ERROR: symbol rte_cfgfile_section_num_entries_by_index is added in the DPDK_20.0 section, but is expected to be added in the EXPERIMENTAL section of the version map
Do you know what it means and how to fix it? The function is not defined as experimental so I don't understand what is the problem
Regards,
Liron
next reply other threads:[~2019-12-17 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 7:36 Liron Himi [this message]
2019-12-17 8:15 ` David Marchand
2019-12-17 8:21 ` [dpdk-dev] [EXT] " Liron Himi
2019-12-17 16:23 ` [dpdk-dev] " Stephen Hemminger
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=MN2PR18MB23989F4988B3B758983DA5C9C6500@MN2PR18MB2398.namprd18.prod.outlook.com \
--to=lironh@marvell.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
--cc=stephen@networkplumber.org \
--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).