WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] linux/usbback: fix usbstub_exit() placement

To: "Noboru Iwamatsu" <n_iwamatsu@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] linux/usbback: fix usbstub_exit() placement
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Fri, 16 Oct 2009 09:38:34 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 16 Oct 2009 01:38:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AD7C5C3.7080001@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4AD730BE020000780001A13C@xxxxxxxxxxxxxxxxxx> <4AD7C5C3.7080001@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Noboru Iwamatsu <n_iwamatsu@xxxxxxxxxxxxxx> 16.10.09 03:00 >>>
>Jan Beulich wrote:
> > The function is being referenced from (non-__exit) usbback_init().
>
>No, usbstub_exit() is only referenced from usbback_exit() in the
>latest version.

Oops, indeed, I didn't recall I had to change this for the 2.6.21 forward
merge. I wonder, however, why I didn't notice the section mismatch
warning earlier...

>Are you suggesting that usbstub_exit() should be referenced from 
>usbback_init() and should do as follows?

Yes, this is what I needed to do there, since I needed to make it return
a value there, as a result of xenbus_register_backend() becoming
__must_check. But really your code, even without the __must_check,
shouldn't ignore failure from xenbus_register_backend().

Jan


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