From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: stable@dpdk.org, dev@dpdk.org, Matan Azrad <matan@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
rasland@mellanox.com, bluca@debian.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] drivers/net: fix mlx* glue libraries ABI version
Date: Thu, 12 Dec 2019 23:17:53 +0100 [thread overview]
Message-ID: <9272526.6B3L8A1auC@xps> (raw)
In-Reply-To: <20191204100546.32095-1-david.marchand@redhat.com>
04/12/2019 11:05, David Marchand:
> Those libraries have been missed when switching to global ABI version.
The versioning of the glue libraries are for compatibility checks
between the PMD and its dependency (rdma-core) packaged as a plugin,
called glue library.
This versioning is updated when there is a change in the verbs glue
interface, in order to avoid issues in case of PMD and glue
updated separately with a non-compatible version.
I don't think the mlx glue libraries are part of the ABI policy
which acts at the application level.
Am I missing something?
next prev parent reply other threads:[~2019-12-12 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 10:05 [dpdk-dev] [PATCH] drivers/net: fix mlx* glue libraries ABI version David Marchand
2019-12-12 22:17 ` Thomas Monjalon [this message]
2020-05-07 12:35 ` [dpdk-dev] [dpdk-stable] " David Marchand
2020-05-07 20:04 ` Thomas Monjalon
2020-10-19 9:41 ` [dpdk-dev] [PATCH v2] drivers: remove mlx* glue libraries separate " David Marchand
2020-10-27 12:13 ` David Marchand
2020-11-01 14:48 ` Thomas Monjalon
2020-11-01 15:02 ` Slava Ovsiienko
2020-11-01 15:09 ` Raslan Darawsheh
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=9272526.6B3L8A1auC@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=rasland@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@mellanox.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.