From: Thomas Monjalon <thomas@monjalon.net>
To: "lironh@marvell.com" <lironh@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH v2] cfgfile: update map file
Date: Mon, 20 Jan 2020 00:31:40 +0100 [thread overview]
Message-ID: <32235274.ATrlOLLGV9@xps> (raw)
In-Reply-To: <DM6PR11MB27149ABF81B72590610CAB06EB500@DM6PR11MB2714.namprd11.prod.outlook.com>
17/12/2019 12:12, Dumitrescu, Cristian:
>
> > -----Original Message-----
> > From: lironh@marvell.com <lironh@marvell.com>
> > Sent: Tuesday, December 17, 2019 11:52 AM
> > To: dev@dpdk.org
> > Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; stable@dpdk.org;
> > Liron Himi <lironh@marvell.com>
> > Subject: [PATCH v2] cfgfile: update map file
> >
> > From: Liron Himi <lironh@marvell.com>
> >
> > rte_cfgfile_section_num_entries_by_index was missing from the map
> > file.
> > meson build failed when calling this function, due to linking a binary to cfgfile
> > built
> > as a shared library
> >
> > Fixes: 85ff364f3b ("build: align symbols with global ABI version")
> >
> > Signed-off-by: Liron Himi <lironh@marvell.com>
>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Fixing the "Fixes" line with the real root cause:
Fixes: 3d2e0448ebb5 ("cfgfile: add section number of entries by index")
Cc: stable@dpdk.org
Applied, thanks
prev parent reply other threads:[~2020-01-19 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 10:43 [dpdk-dev] [PATCH] lib/cfgfile: " lironh
2019-12-17 8:43 ` David Marchand
2019-12-17 11:52 ` [dpdk-dev] [PATCH v2] cfgfile: " lironh
2019-12-17 11:12 ` Dumitrescu, Cristian
2020-01-19 23:31 ` Thomas Monjalon [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=32235274.ATrlOLLGV9@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=lironh@marvell.com \
--cc=stable@dpdk.org \
/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).