RE: [linux-usb-devel] Why double locking the usb-skeleton.c code

2006-01-18 Thread Mukund JB.
Sorry for the siily mistake. Regards, Mukund Jampala > -Original Message- > From: Oliver Neukum [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 18, 2006 3:51 PM > To: linux-usb-devel@lists.sourceforge.net > Cc: Mukund JB. > Subject: Re: [linux-usb-devel] Why doub

Re: [linux-usb-devel] Why double locking the usb-skeleton.c code

2006-01-18 Thread Oliver Neukum
Am Mittwoch, 18. Januar 2006 11:06 schrieb Mukund JB.: > Oliver, > Thanks for the response > > In usb_skeletoc.c sample driver, when I look into the probe function, > When trying for bulk out endpoint, I find the if condition checking for > USB_DIR_IN which I guess is wrong > and it should be

RE: [linux-usb-devel] Why double locking the usb-skeleton.c code

2006-01-18 Thread Mukund JB.
, January 18, 2006 1:46 PM > To: linux-usb-devel@lists.sourceforge.net > Cc: Mukund JB. > Subject: Re: [linux-usb-devel] Why double locking the usb-skeleton.c > code > > > Am Mittwoch, 18. Januar 2006 07:58 schrieb Mukund JB.: > > I made an attempt to understand the USB driver sample cod

Re: [linux-usb-devel] Why double locking the usb-skeleton.c code

2006-01-18 Thread Oliver Neukum
Am Mittwoch, 18. Januar 2006 07:58 schrieb Mukund JB.: > I made an attempt to understand the USB driver sample code in usb-skeleton.c > file /drivers/usb. > I found in the probe function there are two reference counts being maintained. > One is through usb_get_dev() and the other one is kref_init(