DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH 0/3] deprecate attach and detach functions
Date: Wed, 1 Aug 2018 09:26:38 -0700	[thread overview]
Message-ID: <20180801092638.5172583b@xeon-e3> (raw)
In-Reply-To: <1531318450-3942-1-git-send-email-arybchenko@solarflare.com>

On Wed, 11 Jul 2018 15:14:07 +0100
Andrew Rybchenko <arybchenko@solarflare.com> wrote:

> As discussed in [1] EAL hotplug should be used directly to add/remove devices.
> 
> app/pdump changes are build-tested only.
> 
> [1] http://mails.dpdk.org/archives/dev/2018-July/107507.html
> 
> Andrew Rybchenko (3):
>   app/pdump: use hotplug add instead of attach
>   ethdev: deprecate attach and detach functions
>   eal: deprecate device attach and detach functions
> 
>  app/pdump/main.c                        | 94 ++++++++++++++++++-------
>  app/test-pmd/Makefile                   |  1 +
>  app/test-pmd/meson.build                |  1 +
>  doc/guides/rel_notes/deprecation.rst    | 12 ++++
>  lib/librte_eal/common/include/rte_dev.h |  2 +
>  lib/librte_ethdev/rte_ethdev.h          |  2 +
>  6 files changed, 88 insertions(+), 24 deletions(-)
> 

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

  parent reply	other threads:[~2018-08-01 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 14:14 Andrew Rybchenko
2018-07-11 14:14 ` [dpdk-dev] [PATCH 1/3] app/pdump: use hotplug add instead of attach Andrew Rybchenko
2018-07-11 14:14 ` [dpdk-dev] [PATCH 2/3] ethdev: deprecate attach and detach functions Andrew Rybchenko
2018-07-11 14:14 ` [dpdk-dev] [PATCH 3/3] eal: deprecate device " Andrew Rybchenko
2018-07-26 21:32 ` [dpdk-dev] [PATCH 0/3] deprecate " Thomas Monjalon
2018-08-01 16:26 ` Stephen Hemminger [this message]
2018-08-05 23:10   ` Thomas Monjalon

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=20180801092638.5172583b@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --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).