All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	xen-devel@lists.xenproject.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen-pciback: Add MODULE_ALIAS for pciback.
Date: Wed, 26 Nov 2014 11:39:16 -0500	[thread overview]
Message-ID: <CAB=NE6VS9hbk4nTRM7Gw_K6TChiEzDPoPGQ616EK68ASCN8BXQ@mail.gmail.com> (raw)
In-Reply-To: <1408555596.16955.12.camel@hastur.hellion.org.uk>

On Wed, Aug 20, 2014 at 1:26 PM, Ian Campbell <ian.campbell@citrix.com> wrote:
> On Wed, 2014-08-20 at 13:20 -0400, Konrad Rzeszutek Wilk wrote:
>> On Wed, Aug 20, 2014 at 06:18:52PM +0100, Ian Campbell wrote:
>> > On Wed, 2014-08-20 at 12:40 -0400, Konrad Rzeszutek Wilk wrote:
>> > > The rest of the Xen device drivers use an module alias
>> > > to load devices when they shop up in XenBus.
>> >
>> > "show".
>> > >
>> > >  MODULE_LICENSE("Dual BSD/GPL");
>> > >  MODULE_ALIAS("xen-backend:pci");
>> > > +MODULE_ALIAS("xen:pci");
>> >
>> > Isn't that xen-backend:pci already the right thing for a backend device?
>> > xen: is for frontends, I thought.
>>
>> Oh, you are right. Cool! Thanks!
>
> The patch turned out to be even more trivial than expected ;-)

Is this what we expected to be pending work for the item "device
hotplug (MODULE_ALIAS)" on the upstream TODO list?

http://wiki.xenproject.org/wiki/XenParavirtOps#Upstream_delta_details

This was simply to just auto load that driver when needed right?

Also as for actual PCI device hotplug support:

http://wiki.xen.org/wiki/Xen_PCI_Passthrough#Hotplug

I don't think we need a delta for that do we?

 Luis

  parent reply	other threads:[~2014-11-26 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 16:40 [PATCH] Add MODULE_ALIAS for Xen pciback. (v1) Konrad Rzeszutek Wilk
2014-08-20 16:40 ` [PATCH] xen-pciback: Add MODULE_ALIAS for pciback Konrad Rzeszutek Wilk
2014-08-20 17:18   ` [Xen-devel] " Ian Campbell
2014-08-20 17:20     ` Konrad Rzeszutek Wilk
2014-08-20 17:20     ` [Xen-devel] " Konrad Rzeszutek Wilk
2014-08-20 17:26       ` Ian Campbell
2014-08-20 17:26       ` [Xen-devel] " Ian Campbell
2014-11-26 16:39         ` Luis R. Rodriguez
2014-11-26 16:39         ` Luis R. Rodriguez [this message]
2014-08-20 17:18   ` Ian Campbell
2014-08-20 16:40 ` Konrad Rzeszutek Wilk
2014-11-26 17:18 [Xen-devel] " Konrad Rzeszutek Wilk

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='CAB=NE6VS9hbk4nTRM7Gw_K6TChiEzDPoPGQ616EK68ASCN8BXQ@mail.gmail.com' \
    --to=mcgrof@do-not-panic.com \
    --cc=ian.campbell@citrix.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 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.