patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdk stable <stable@dpdk.org>, Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [dpdk-stable] [PATCH 18.11] Revert "common/octeontx: add missing public symbol"
Date: Mon, 02 Mar 2020 10:45:01 +0000	[thread overview]
Message-ID: <07c6a3d18377616d23eea08e8ca999acc28755fc.camel@debian.org> (raw)
In-Reply-To: <CAJFAV8x4cj+A_079Nr_U8=pL61wFaABTOr1=gH6Ni2rp-hNhDw@mail.gmail.com>

On Mon, 2020-03-02 at 11:23 +0100, David Marchand wrote:
> On Fri, Feb 28, 2020 at 7:20 PM <
> luca.boccassi@gmail.com
> > wrote:
> > From: Luca Boccassi <
> > luca.boccassi@microsoft.com
> > >
> > 
> > This reverts commit bd979fff652326e042c21aaaf3df1f515ffdff6e.
> > 
> > It changed the public symbol version from @Base to @DPDK_18.05,
> > breaking ABI compatibility.
> 
> This symbol is exported through private macro logs used by octeontx
> drivers.
> The drivers are all built at once and released together.
> 
> The symbol is not exported in a public header.
> This is not an application ABI breakage.

It is part of the list of public symbols exposed by the shared object.
Whether it is used or not, as a matter of policy, I cannot upload a new
LTS release to Debian/Ubuntu if it removes/changes a public symbol.

-- 
Kind regards,
Luca Boccassi

      reply	other threads:[~2020-03-02 10:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28 18:20 luca.boccassi
2020-02-28 18:33 ` Kevin Traynor
2020-03-02 10:23 ` David Marchand
2020-03-02 10:45   ` Luca Boccassi [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=07c6a3d18377616d23eea08e8ca999acc28755fc.camel@debian.org \
    --to=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=ktraynor@redhat.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).