[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] USB virt 2.6 split driver patch series


  • To: harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
  • From: NAHieu <nahieu@xxxxxxxxx>
  • Date: Tue, 22 Nov 2005 11:00:23 +0900
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 22 Nov 2005 02:00:21 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DvZnO9r24Y7ntBxHhcZI7QwtLTPDw61YJJw+Q/VijYqOr6OMcqupIZC4XWQd+lqQnmlNCa/Ak64UoxcAQPhVgmEQi4UPgaDQdA3pl6piFaTBm6CuD41cIZsK4IH4WAMKklMVNnXi/TBn53mkktIuDYPsBQW8rfCuj9azYXeHbpk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 11/22/05, NAHieu <nahieu@xxxxxxxxx> wrote:
> I had a look at xenidc code, and found some code like this:
>
> --
> static void xenidc_endpoint_destroy_1(xenidc_callback * callback)
> {
>         trace();
>
>         {
>                 xenidc_endpoint_callback *endpoint_callback =
>                     container_of(callback, xenidc_endpoint_callback, 
> callback);
>
>                 endpoint_callback->destroyed = 1;
>
>                 xenidc_work_wake_up();
>         }
> }
> --
>
> Why name it *destroy_1? it is a common practice to name a local
> function with _ or __ as prefix. So for example
> xenidc_endpoint_destroy_1() should be named
> _xenidc_endpoint_destroy_1() or __xenidc_endpoint_destroy_1()
>

Oops, typo. I meant _xenidc_endpoint_destroy_1() should be named
_xenidc_endpoint_destroy() or __xenidc_endpoint_destroy()

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.