From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>, dev <dev@dpdk.org>,
rasland@mellanox.com
Subject: Re: [dpdk-dev] [PATCH] ethdev: add field for device data per process
Date: Fri, 05 Oct 2018 16:47:50 +0200 [thread overview]
Message-ID: <1899489.eb9E0yuFE2@xps> (raw)
In-Reply-To: <0c1f4fbe-9e34-9c69-10c9-46f6d5df9ca2@intel.com>
05/10/2018 15:26, Ferruh Yigit:
> On 10/5/2018 2:17 PM, Alejandro Lucero wrote:
> > On Fri, Oct 5, 2018 at 2:01 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> >> Will there be new version?
> >>
> >> Are we agree on name?
> >>
> >> Is LIBABIVER increase should be done in this patch, or will there be other
> >> patch
> >> already doing it?
> >>
> >
> > I'm not familiar with LIBABIVER but just tell me to send it again with that
> > change if you consider that is the right thing to do.
>
> ABI breakage process:
> - Increase LIBABIVER in library Makefile/meson.build
> - Update lib in release notes "Shared Library Versions" section, with a "+" to
> to indicate change
> - Remove deprecation notice (seems not applies to this one)
>
> Thomas mentioned there is another patch breaking the ABI for ethdev, I wonder
> which patch will do the above process.
There will be a patch to remove the attach/detach function.
But the patch for data per process will probably be applied first.
Please do the LIBABIVER bump as described by Ferruh.
prev parent reply other threads:[~2018-10-05 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 11:26 Alejandro Lucero
2018-10-03 20:44 ` Thomas Monjalon
2018-10-04 11:31 ` Ferruh Yigit
2018-10-05 13:01 ` Ferruh Yigit
2018-10-05 13:17 ` Alejandro Lucero
2018-10-05 13:26 ` Ferruh Yigit
2018-10-05 14:47 ` Thomas Monjalon [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=1899489.eb9E0yuFE2@xps \
--to=thomas@monjalon.net \
--cc=alejandro.lucero@netronome.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=rasland@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 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).