From: nardelli <jnardelli@infosciences.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH] visor: Fix Oops on disconnect
Date: Fri, 21 May 2004 13:08:45 -0400 [thread overview]
Message-ID: <40AE379D.9090401@infosciences.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0405211103350.651-100000@ida.rowland.org>
Alan Stern wrote:
> On Fri, 21 May 2004, nardelli wrote:
>
>
>>The api for usb_control_msg says, 'If successful, it returns 0, othwise a
>>negative error number', and I didn't see any other way to figure out how
>>much data was being returned.
>
>
> In the current kernel sources, the kerneldoc for usb_control_msg() says
> "If successful, it returns the number of bytes transferred, otherwise a
> negative error number."
>
Sorry, I was looking at dated api docs at kernelnewbies.org. I'll use
the size returned from usb_control_msg() instead of memset().
--
Joe Nardelli
jnardelli@infosciences.com
next prev parent reply other threads:[~2004-05-21 17:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 23:08 [PATCH] visor: Fix Oops on disconnect nardelli
2004-05-21 4:30 ` [linux-usb-devel] " Greg KH
2004-05-21 5:03 ` Pete Zaitcev
2004-05-21 14:52 ` nardelli
2004-05-21 14:48 ` nardelli
2004-05-21 15:05 ` Alan Stern
2004-05-21 17:08 ` nardelli [this message]
2004-05-21 15:41 ` Greg KH
2004-05-21 19:51 ` nardelli
2004-05-21 20:01 ` jkroon
2004-05-21 20:22 ` nardelli
2004-05-21 20:44 ` Greg KH
2004-05-21 21:44 ` nardelli
2004-05-21 21:56 ` Greg KH
2004-05-21 22:04 ` nardelli
2004-05-21 22:30 ` Greg KH
2004-05-24 17:20 ` nardelli
2004-05-24 19:38 ` nardelli
2004-05-24 20:06 ` Greg KH
2004-05-24 20:21 ` nardelli
2004-05-25 13:15 ` nardelli
2004-05-24 20:08 ` Greg KH
2004-05-24 21:42 ` nardelli
2004-05-25 18:30 ` Greg KH
2004-05-25 18:55 ` nardelli
2004-05-21 4:31 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40AE379D.9090401@infosciences.com \
--to=jnardelli@infosciences.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.