From: David Marchand <david.marchand@redhat.com>
To: Ray Kinsella <mdr@ashroe.eu>
Cc: Dodji Seketeli <dodji@redhat.com>, dev <dev@dpdk.org>,
Andrzej Ostruszka <aostruszka@marvell.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas@monjalon.net>,
Neil Horman <nhorman@tuxdriver.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Matan Azrad <matan@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
Jerin Jacob <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Alfredo Cardigliano <cardigliano@ntop.org>,
Mahipal Challa <mchalla@marvell.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
"Wang, Haiyue" <haiyue.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] abi: change references to abi 20.0.1 to abi v21
Date: Fri, 24 Apr 2020 17:01:45 +0200 [thread overview]
Message-ID: <CAJFAV8z_ieVjAFHq7-9LFYygvxyJLa32=AE9AHJcGLNrx2mmZw@mail.gmail.com> (raw)
In-Reply-To: <2d93bafb-0909-fcb8-5900-664a68088682@ashroe.eu>
On Fri, Apr 24, 2020 at 4:50 PM Ray Kinsella <mdr@ashroe.eu> wrote:
>
> ah ok, the particular system I made the change on was Ubuntu 18.04.2.
> which is libabigail 1.2.0.
>
> Given we still support v19.11 on Ubuntu 18.04.2.
> I think it's worthwhile keeping the suppression until v20.11?
1.2 is fairly old and does not seem maintained by Ubuntu (asked for
backport, and got ignored so far).
https://bugs.launchpad.net/ubuntu/+source/libabigail/+bug/1863607
Dodji told me that there were new checks added in newer sersions.
I also fear that supporting an old libabigail version will force us to
add a lot of other rules.
In Travis, we currently use libabigail 1.6 (mainly because I did not
update to 1.7 when it was released).
--
David Marchand
next prev parent reply other threads:[~2020-04-24 15:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 9:34 [dpdk-dev] [PATCH] " Ray Kinsella
2020-04-20 11:57 ` Ray Kinsella
2020-04-20 12:20 ` David Marchand
2020-04-20 15:25 ` Ray Kinsella
2020-04-22 8:07 ` Ray Kinsella
2020-04-22 8:11 ` David Marchand
2020-04-22 8:18 ` Thomas Monjalon
2020-04-22 8:28 ` Ray Kinsella
2020-04-23 6:41 ` [dpdk-dev] [PATCH v2] " Ray Kinsella
2020-04-24 9:15 ` Thomas Monjalon
2020-04-24 14:10 ` David Marchand
2020-04-24 14:50 ` Ray Kinsella
2020-04-24 15:01 ` David Marchand [this message]
2020-04-29 12:19 ` Dodji Seketeli
2020-04-30 8:23 ` Ray Kinsella
2020-04-27 9:06 ` [dpdk-dev] [PATCH v3] " Ray Kinsella
2020-04-27 9:06 ` Ray Kinsella
2020-04-27 13:45 ` [dpdk-dev] [PATCH v4] " Ray Kinsella
2020-04-27 13:45 ` Ray Kinsella
2020-04-30 10:21 ` [dpdk-dev] [PATCH v5] " Ray Kinsella
2020-04-30 10:27 ` [dpdk-dev] [PATCH v6 1/1] " Ray Kinsella
2020-04-30 10:27 ` Ray Kinsella
2020-05-04 22:23 ` Thomas Monjalon
2020-05-04 22:05 ` 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='CAJFAV8z_ieVjAFHq7-9LFYygvxyJLa32=AE9AHJcGLNrx2mmZw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aostruszka@marvell.com \
--cc=cardigliano@ntop.org \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=dodji@redhat.com \
--cc=haiyue.wang@intel.com \
--cc=jerinj@marvell.com \
--cc=jingjing.wu@intel.com \
--cc=matan@mellanox.com \
--cc=mchalla@marvell.com \
--cc=mdr@ashroe.eu \
--cc=ndabilpuram@marvell.com \
--cc=nhorman@tuxdriver.com \
--cc=shahafs@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@mellanox.com \
--cc=wenzhuo.lu@intel.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).