From: Ray Kinsella <mdr@ashroe.eu>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, "Wang, Haiyue" <haiyue.wang@intel.com>,
Matan Azrad <matan@mellanox.com>,
Anoob Joseph <anoobj@marvell.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Mahipal Challa <mchalla@marvell.com>,
Eelco Chaudron <echaudro@redhat.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jingjing Wu <jingjing.wu@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Alfredo Cardigliano <cardigliano@ntop.org>,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] [PATCH] abi: change references to abi 20.0.1 to abi v21
Date: Mon, 20 Apr 2020 16:25:07 +0100 [thread overview]
Message-ID: <c66284eb-d0aa-4cc1-85a0-a2ddcebe9a5b@ashroe.eu> (raw)
In-Reply-To: <CAJFAV8za9YGcRvgZPtGufVm71YDc6=H5MXNvvcV3-KzTu+X+AQ@mail.gmail.com>
On 20/04/2020 13:20, David Marchand wrote:
> On Mon, Apr 20, 2020 at 1:57 PM Ray Kinsella <mdr@ashroe.eu> wrote:
>>
>> Travis ABI check warnings, can be safely ignored in this case, I think.
>>
>> https://travis-ci.com/github/ovsrobot/dpdk/builds/161009923
>
> How about comparing to 19.11 ABI then?
Theory is we should always be checking against v19.11 abi.
So this _should_ be v19.11 ...
I will change in v2 and see what it throws up.
>
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -36,7 +36,7 @@ script: ./.ci/${TRAVIS_OS_NAME}-build.sh
>
> env:
> global:
> - - REF_GIT_TAG=v20.02
> + - REF_GIT_TAG=v19.11
>
> jobs:
> include:
>
>
next prev parent reply other threads:[~2020-04-20 15:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 9:34 Ray Kinsella
2020-04-20 11:57 ` Ray Kinsella
2020-04-20 12:20 ` David Marchand
2020-04-20 15:25 ` Ray Kinsella [this message]
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
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=c66284eb-d0aa-4cc1-85a0-a2ddcebe9a5b@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=anoobj@marvell.com \
--cc=cardigliano@ntop.org \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=echaudro@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=haiyue.wang@intel.com \
--cc=jerinj@marvell.com \
--cc=jingjing.wu@intel.com \
--cc=matan@mellanox.com \
--cc=mchalla@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=nhorman@tuxdriver.com \
--cc=shahafs@mellanox.com \
--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).