DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: gaetan.rivet@6wind.com, ferruh.yigit@intel.com,
	arybchenko@solarflare.com, wisamm@mellanox.com,
	ophirmu@mellanox.com
Subject: Re: [dpdk-dev] [PATCH] devargs: fix freeing during device removal
Date: Fri, 19 Oct 2018 22:53:19 +0200	[thread overview]
Message-ID: <3515806.AfmK2v9imX@xps> (raw)
In-Reply-To: <20181018001949.17443-1-thomas@monjalon.net>

18/10/2018 02:19, Thomas Monjalon:
> After calling unplug function of a bus, the device is expected
> to be freed. It is too late for getting devargs to remove.
> Anyway, the buses which implement unplug are already freeing
> the devargs, except the PCI bus.
> So the call to rte_devargs_remove() is removed from EAL and
> added in PCI.
> 
> Fixes: 2effa126fbd8 ("devargs: simplify parameters of removal function")
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>

Applied

      reply	other threads:[~2018-10-19 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18  0:19 Thomas Monjalon
2018-10-19 20:53 ` 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=3515806.AfmK2v9imX@xps \
    --to=thomas@monjalon.net \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gaetan.rivet@6wind.com \
    --cc=ophirmu@mellanox.com \
    --cc=wisamm@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).