xen-devel

[Top] [All Lists]

[Xen-devel] unexported xenbus_register_backend ?

from [Himanshu Raj]

[Permanent Link][Original]

To:	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-devel] unexported xenbus_register_backend ?
From:	Himanshu Raj <rhim@xxxxxxxxxxxxx>
Date:	Tue, 18 Oct 2005 14:18:26 -0400
Delivery-date:	Tue, 18 Oct 2005 18:15:44 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mutt/1.4.2.1i

Hi Folks,

Is there a particular reason not to export xenbus_register_backend? Sort of easy
to develop a separate backend module without polluting xenolinux src tree. 

-Himanshu

-- 
-------------------------------------------------------------------------
Himanshu Raj
PhD Student, GaTech (www.cc.gatech.edu/~rhim)
I prefer to receive attachments in an open, non-proprietary format.
-------------------------------------------------------------------------

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] unexported xenbus_register_backend ?, Himanshu Raj <=

Previous by Date:	Re: [Xen-devel] Bugs with block devices to domU - let's find solution, Stephan Boni
Next by Date:	[Xen-devel] SMP on X86, peter Bier
Previous by Thread:	[Xen-devel] Bugs with block devices to domU - let's find solution, Guryanov Dmitry
Next by Thread:	[Xen-devel] SMP on X86, peter Bier
Indexes:	[Date] [Thread] [Top] [All Lists]