From: Bastian Blank Subject: Re: [Xen-devel] [PATCH 3/4] xen: Add xenbusd device driver Date: Thu, 8 Dec 2011 10:27:58 +0100 Message-ID: <20111208092757.GA22678@wavehammer.waldi.eu.org> References: <1323292396-19523-1-git-send-email-waldi@debian.org> <1323292396-19523-4-git-send-email-waldi@debian.org> <1323332686.2969.49.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <1323332686.2969.49.camel@zakaz.uk.xensource.com> Sender: linux-kernel-owner@vger.kernel.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , "linux-kernel@vger.kernel.org" , "konrad.wilk@oracle.com" List-Id: xen-devel@lists.xenproject.org On Thu, Dec 08, 2011 at 08:24:46AM +0000, Ian Campbell wrote: > On Wed, 2011-12-07 at 21:13 +0000, Bastian Blank wrote: > > +obj-$(CONFIG_XEN_BACKEND) += xenbus_dev_backend.o > In principal this could be its own module which does not depend on any > of the backend stuff but I think this is fine for now. I even think about registering this device from xenstored_local_init in xenbus_probe.c. Then it will be available only if the kernel also owns the communcation ring. > "Could not register xenbus backend device" to distinguish from the f.e. > failure message, you could also add "frontend" there I suppose. Other > than that: Yep. Will someone mind if I rename this device to xenbus_backend? It's more clear. Bastian -- Deflector shields just came on, Captain.