From: Stephen Hemminger <stephen@networkplumber.org>
To: Liron Himi <lironh@marvell.com>
Cc: dpdk-dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] checkpatch failing on map change
Date: Tue, 17 Dec 2019 08:23:02 -0800 [thread overview]
Message-ID: <20191217082302.37e24da8@hermes.lan> (raw)
In-Reply-To: <MN2PR18MB23989F4988B3B758983DA5C9C6500@MN2PR18MB2398.namprd18.prod.outlook.com>
On Tue, 17 Dec 2019 07:36:20 +0000
Liron Himi <lironh@marvell.com> wrote:
> 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
It means checkpatch is not infallible. It is only an advisor.
In this case, it doesn't understand how to deal with a bug fix.
prev parent reply other threads:[~2019-12-17 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 7:36 [dpdk-dev] checkpatch failing on map change Liron Himi
2019-12-17 8:15 ` David Marchand
2019-12-17 8:21 ` [dpdk-dev] [EXT] " Liron Himi
2019-12-17 16:23 ` Stephen Hemminger [this message]
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=20191217082302.37e24da8@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=lironh@marvell.com \
--cc=nhorman@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.