DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Matan Azrad <matan@nvidia.com>,
	Shahaf Shuler <shahafs@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	rasland@nvidia.com, asafp@nvidia.com
Subject: Re: [dpdk-dev] [PATCH v2] drivers: remove mlx* glue libraries separate ABI version
Date: Sun, 01 Nov 2020 15:48:38 +0100	[thread overview]
Message-ID: <6054877.ONCYLs7J70@thomas> (raw)
In-Reply-To: <20201019094151.30185-1-david.marchand@redhat.com>

19/10/2020 11:41, David Marchand:
> The glue libraries are tightly bound to the mlx drivers of a dpdk version
> and are packaged with them.
> 
> Keeping a separate ABI version prevents us from installing two versions of
> dpdk.
> Maintaining this separate version just adds confusion.
> Align the glue library ABI version to the global ABI version.
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>

There was no comment after 2 weeks, it should be merged.

Acked-by: Thomas Monjalon <thomas@monjalon.net>




  parent reply	other threads:[~2020-11-01 14:48 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 " David Marchand
2019-12-12 22:17 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2020-05-07 12:35   ` 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 [this message]
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=6054877.ONCYLs7J70@thomas \
    --to=thomas@monjalon.net \
    --cc=asafp@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=viacheslavo@nvidia.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).