LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: nardelli <jnardelli@infosciences.com>
To: Greg KH <greg@kroah.com>
Cc: 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 17:44:09 -0400 [thread overview]
Message-ID: <40AE7829.9060105@infosciences.com> (raw)
In-Reply-To: <20040521204430.GA5875@kroah.com>
Greg KH wrote:
> On Fri, May 21, 2004 at 03:51:23PM -0400, nardelli wrote:
>
>
> Patch is line-wrapped, so I can't apply it :(
>
>
Hmmm... I couldn't see the linewrap in the original I sent, or
in test ones that I did. Probably my mail tool, but then it
is getting late on a Friday, which probably means that it is me.
To aid in diagnosing where I'm goofing up, could you point out
a spot where it is linewrapping?
>>@@ -456,7 +460,8 @@ static void visor_close (struct usb_seri
>> return;
>>
>> /* shutdown our urbs */
>>- usb_unlink_urb (port->read_urb);
>>+ if (port->read_urb)
>>+ usb_unlink_urb (port->read_urb);
>
>
> I really do not think these extra checks for read_urb all of the place
> need to be added. We take care of it in the open() call, right?
>
>
>
Yes - less clutter and more efficient too.
>>+ else if (retval != sizeof(*connection_info)) {
>>+ /* real invalid connection info handling is below */
>>+ num_ports = 0;
>>+ }
>
>
> Change this to a "if" instead of a "else if".
> Actually just set num_ports to 0 at the beginning of the function, and
> then just check for a valud retval and do the code below...
>
>
Yep - same comment as above.
>>+ else {
>>+ connection_info = (struct visor_connection_info *)
>>+ transfer_buffer;
>
>
>
> greg k-h
>
--
Joe Nardelli
jnardelli@infosciences.com
next prev parent reply other threads:[~2004-05-21 21:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 23:08 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
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 [this message]
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=40AE7829.9060105@infosciences.com \
--to=jnardelli@infosciences.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--subject='Re: [linux-usb-devel] [PATCH] visor: Fix Oops on disconnect' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).