DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>, Aaron Conole <aconole@redhat.com>,
	 Michael Santana <maicolgabriel@hotmail.com>,
	Dodji Seketeli <dodji@redhat.com>
Subject: Re: [PATCH] version: 22.03-rc0
Date: Thu, 2 Dec 2021 17:13:51 +0100	[thread overview]
Message-ID: <CAJFAV8w3QWZugfWmWhKAWMLnXU23y2HjdSEpCJHVj5s7U1yp9w@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yqk0dUkj58rSxtUcHNd21jaC4mj2Qh8gGYhBk_U4Q63w@mail.gmail.com>

On Tue, Nov 30, 2021 at 8:51 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Tue, Nov 30, 2021 at 4:35 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > 29/11/2021 14:16, David Marchand:
> > > Start a new release cycle with empty release notes.
> > > Bump version and ABI minor.
> > > Enable ABI checks using latest libabigail.
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > [...]
> > > -      LIBABIGAIL_VERSION: libabigail-1.8
> > > +      LIBABIGAIL_VERSION: libabigail-2.0
> >
> > What is the reason for this update? Can we still use the old version?
>
> Nothing prevents from using the old version, I just used this chance
> to bump the version.
>
> I talked with Dodji, 2.0 is the version used in Fedora for ABI checks.
> This version comes with enhancements and at least a fix for a bug we
> got when writing exception rules in dpdk:
> https://sourceware.org/bugzilla/show_bug.cgi?id=28060

I ran more checks with 2.0 and unfortunately, I get an issue with dpdk
on Fedora 35 libabigail.
2.0 built in Ubuntu does not seem affected, but I prefer to be safe,
stick to 1.8 version and wait for Dodji to have a look.

v2 on the way.


-- 
David Marchand


  reply	other threads:[~2021-12-02 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29 13:16 David Marchand
2021-11-30 15:35 ` Thomas Monjalon
2021-11-30 19:51   ` David Marchand
2021-12-02 16:13     ` David Marchand [this message]
2021-12-02 18:11 ` [PATCH v2] " David Marchand
2021-12-02 19:34   ` Thomas Monjalon
2021-12-02 20:36   ` David Marchand

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=CAJFAV8w3QWZugfWmWhKAWMLnXU23y2HjdSEpCJHVj5s7U1yp9w@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dodji@redhat.com \
    --cc=maicolgabriel@hotmail.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 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).