public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
	<boris.ostrovsky@oracle.com>, <jbeulich@suse.com>
Subject: Re: [PATCH v1] Documentation and two bug-fixes for Xen pciback.
Date: Wed, 30 Apr 2014 17:25:55 +0100	[thread overview]
Message-ID: <53612413.7000801@citrix.com> (raw)
In-Reply-To: <1398866051-32714-1-git-send-email-konrad.wilk@oracle.com>

On 30/04/14 14:54, Konrad Rzeszutek Wilk wrote:
> Hey,
> 
> This patchset is just a simple documentation and two bug-fixes
> to the Xen pciback. I am still looking at implementing the proper
> way of doing reset for the devices - based on David's feedback - but
> that is going to take a big of time. In the meantime this patchset
> is presented as today is the documentation day!
> 
> 
>  drivers/xen/xen-pciback/pci_stub.c | 25 +++++++++++++++++++------
>  drivers/xen/xen-pciback/xenbus.c   |  4 ++++
>  2 files changed, 23 insertions(+), 6 deletions(-)
> 
> Konrad Rzeszutek Wilk (6):
>       xen-pciback: Cleanup up pcistub_put_pci_dev
>       xen-pciback: First reset, then free.
>       xen-pciback: Document when we FLR an PCI device.
>       xen/pciback: Document when the 'unbind' and 'bind' functions are called.
>       xen/pciback: Document the entry points for 'pcistub_put_pci_dev'

These:

Reviewed-by: David Vrabel <david.vrabel@citrix.com>

>       xen/pciback: Don't call xen_pcibk_config_init_dev when device
de-assigned.

Could you just check that nothing relied on the dyn_fields() being
deleted here.

David

      parent reply	other threads:[~2014-04-30 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 13:54 [PATCH v1] Documentation and two bug-fixes for Xen pciback Konrad Rzeszutek Wilk
2014-04-30 13:54 ` [PATCH v1 1/6] xen-pciback: Cleanup up pcistub_put_pci_dev Konrad Rzeszutek Wilk
2014-04-30 13:54 ` [PATCH v1 2/6] xen-pciback: First reset, then free Konrad Rzeszutek Wilk
2014-04-30 13:54 ` [PATCH v1 3/6] xen-pciback: Document when we FLR an PCI device Konrad Rzeszutek Wilk
2014-04-30 13:54 ` [PATCH v1 4/6] xen/pciback: Document when the 'unbind' and 'bind' functions are called Konrad Rzeszutek Wilk
2014-04-30 13:54 ` [PATCH v1 5/6] xen/pciback: Document the entry points for 'pcistub_put_pci_dev' Konrad Rzeszutek Wilk
2014-04-30 13:54 ` [PATCH v1 6/6] xen/pciback: Don't call xen_pcibk_config_init_dev when device de-assigned Konrad Rzeszutek Wilk
2014-04-30 14:40   ` Jan Beulich
2014-04-30 16:25 ` David Vrabel [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=53612413.7000801@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jbeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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