All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com, ian.campbell@citrix.com,
	Ian Campbell <ijc@hellion.org.uk>
Subject: Re: [PATCH 3/3] xen: rename pciback module to xen-pciback.
Date: Thu, 3 Dec 2009 17:20:48 -0500	[thread overview]
Message-ID: <20091203222048.GA21940@phenom.dumpdata.com> (raw)
In-Reply-To: <4B1836F4.8080705@goop.org>

On Thu, Dec 03, 2009 at 02:08:52PM -0800, Jeremy Fitzhardinge wrote:
> On 12/03/09 14:02, Konrad Rzeszutek Wilk wrote:
>> On Thu, Dec 03, 2009 at 09:56:20PM +0000, ian.campbell@citrix.com wrote:
>>    
>>> pciback is rather generic for a modular distro style kernel.
>>>      
>> Do you have a patch for Xen python stack to check ownership of
>> PCI devices to also be 'xen-pciback'?
>>    
>
> Is the module name the same as the driver name?

Not with this patch. The driver name is 'pciback' but the module name
will be 'xen-pciback'. I am not sure how that is going to resolve
in SysFS - hopefully it will remain 'pciback' for the pertient directories.

  reply	other threads:[~2009-12-03 22:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 21:56 Rename backend modules to be less generic ian.campbell
2009-12-03 21:56 ` [PATCH 1/3] xen: rename blkbk module xen-blkback ian.campbell
2009-12-03 21:56 ` [PATCH 2/3] xen: rename netbk module xen-netback ian.campbell
2009-12-03 21:56 ` [PATCH 3/3] xen: rename pciback module to xen-pciback ian.campbell
2009-12-03 22:02   ` Konrad Rzeszutek Wilk
2009-12-03 22:08     ` Jeremy Fitzhardinge
2009-12-03 22:20       ` Konrad Rzeszutek Wilk [this message]
2009-12-03 22:14     ` Ian Campbell
2009-12-03 22:18       ` Jeremy Fitzhardinge

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=20091203222048.GA21940@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=ijc@hellion.org.uk \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.