All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>, Ray Kinsella <mdr@ashroe.eu>
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>,
	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: Wed, 22 Apr 2020 10:18:04 +0200	[thread overview]
Message-ID: <2825922.687JKscXgg@thomas> (raw)
In-Reply-To: <9fdccceb-d667-0418-ddda-1584c76991cf@ashroe.eu>

22/04/2020 10:07, Ray Kinsella:
> 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?
> > 
> Concluded on separate thread it is best to leave this as v20.02.

It means the ABI tool will be reporting a failure?
The tool needs to reliably report zero false positive.
How can we mitigate this issue? 



  parent reply	other threads:[~2020-04-22  8:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  9:34 [dpdk-dev] [PATCH] abi: change references to abi 20.0.1 to abi v21 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 [this message]
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=2825922.687JKscXgg@thomas \
    --to=thomas@monjalon.net \
    --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=mdr@ashroe.eu \
    --cc=ndabilpuram@marvell.com \
    --cc=nhorman@tuxdriver.com \
    --cc=shahafs@mellanox.com \
    --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 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.