DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Raz Amir <razamir22@gmail.com>,
	Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] pci: save list of detached devices, and re-probe during driver unload
Date: Thu, 09 Jul 2015 00:51:10 +0200	[thread overview]
Message-ID: <1460734.qdGxFBnQ8D@xps13> (raw)
In-Reply-To: <6544717.r8ii0elbbK@xps13>

This patch received no more comment about a common BSD/Linux behaviour.
Maybe that some documentation is needed.

2015-03-16 17:29, Thomas Monjalon:
> Hi,
> 
> 2015-03-12 14:24, Raz Amir:
> > Thank you.
> > Can you tell when will the patch be pushed to the source code?
> 
> This is changing the behaviour. I think we should keep it for 2.1 and check if
> some docs must be updated in the meantime.
> Then we should look at general behaviour for binding/unbinding devices in DPDK.
> I feel it would be better to have a common behaviour with BSD, Linux UIO,
> Linux VFIO, etc.
> 
> > -----Original Message-----
> > From: Bruce Richardson [mailto:bruce.richardson@intel.com] 
> > Sent: 11 March 2015 12:26
> > To: Raz Amir
> > Cc: dev@dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH v4] pci: save list of detached devices, and
> > re-probe during driver unload
> > 
> > On Thu, Mar 05, 2015 at 06:24:23PM +0200, Raz Amir wrote:
> > > Added code that saves the pointers to the detached devices, during 
> > > driver loading, and during driver unloading, go over the list, and 
> > > re-attach them by calling device_probe_and_attach on each device.
> > > 
> > > Signed-off-by: Raz Amir <razamir22@gmail.com>
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied, thanks

      reply	other threads:[~2015-07-08 22:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  6:33 [dpdk-dev] [PATCH] " Raz Amir
2015-03-01 13:48 ` Neil Horman
2015-03-01 14:21   ` Raz Amir
2015-03-01 17:16     ` Neil Horman
2015-03-02  8:18       ` Raz Amir
2015-03-02 11:36         ` Neil Horman
2015-03-02 11:58           ` Raz Amir
2015-03-02 13:29             ` Thomas Monjalon
2015-03-03 11:30               ` Raz Amir
2015-03-03 11:45                 ` Bruce Richardson
2015-03-03 12:56                   ` Raz Amir
2015-03-03 13:32 ` Bruce Richardson
2015-03-04  9:07   ` Raz Amir
2015-03-04 10:13     ` Bruce Richardson
2015-03-04 10:28       ` Raz Amir
2015-03-04 11:15 ` [dpdk-dev] [PATCH v3] " Raz Amir
2015-03-09  8:07   ` Raz Amir
2015-03-09 10:27     ` Bruce Richardson
2015-03-10  8:15       ` Raz Amir
2015-03-04 11:47 ` [dpdk-dev] [PATCH v2] " Raz Amir
2015-03-05 14:59 ` [dpdk-dev] [PATCH v4] " Raz Amir
2015-03-05 16:24 ` Raz Amir
2015-03-11 10:26   ` Bruce Richardson
2015-03-12 12:24     ` Raz Amir
2015-03-16 16:29       ` Thomas Monjalon
2015-07-08 22:51         ` 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=1460734.qdGxFBnQ8D@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=razamir22@gmail.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).