All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Tilman Schmidt <tilman@imap.cc>,
	linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Status of Bug 8094 -  ipaq oops on connecting "Vodafone VPA-II" ?
Date: Sun, 20 Sep 2009 11:11:33 -0700	[thread overview]
Message-ID: <20090920181133.GA14366@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0909201308550.8307-100000@netrider.rowland.org>

On Sun, Sep 20, 2009 at 01:12:29PM -0400, Alan Stern wrote:
> On Sun, 20 Sep 2009, Greg KH wrote:
> 
> > On Sun, Sep 20, 2009 at 03:39:57PM +0200, Tilman Schmidt wrote:
> > > When I connect my "T-Mobile MDA compact III" to my PC, running
> > > kernel 2.6.31 with openSUSE 10.3 userspace, I get exactly the
> > > symptoms described in:
> > > 
> > > http://bugzilla.kernel.org/show_bug.cgi?id=8094
> > > 
> > > But that bug is marked as "CLOSED CODE_FIX", though reading through
> > > the comments I found no clear indication what was actually fixed,
> > > and from reading through the source files drivers/usb/serial/ipaq.c
> > > and drivers/usb/serial/usb-serial.c I get the impression that the
> > > problem of ipaq_open() oopsing because it gets called with
> > > port->read_urb==NULL is still present.
> 
> Interestingly, the fix from that bug report _was_ merged as commit
> 063a2da8f01806906f7d7b1a1424b9afddebc443 (written by me).  But then it
> was removed later on(!) in commits
> 07c3b1a1001614442c665570942a3107a722c314 and
> 9aebfd6bda789891e6d296bb49b5fb32d1057f18 (written by Greg).
> 
> Apparently the check should have been moved from the core into the 
> lower-level driver (i.e., ipaq.c) but it wasn't.  I don't know why; 
> maybe Greg does.

Yes, I missed the fact that the ipaq driver needed to pay attention to
this, my mistake :(

I'm pretty much not able to write any new patches until the end of next
week, due to conferences I'm currently attending, so if someone wants to
knock up a patch to fix this before then, it would be most appreciated.

thanks,

greg k-h

  reply	other threads:[~2009-09-20 18:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20 13:39 Status of Bug 8094 - ipaq oops on connecting "Vodafone VPA-II" ? Tilman Schmidt
2009-09-20 15:05 ` Greg KH
2009-09-20 16:28   ` Tilman Schmidt
2009-09-20 16:37     ` Arjan van de Ven
2009-09-20 16:51       ` Tilman Schmidt
2009-09-20 17:32         ` Arjan van de Ven
2009-09-20 17:01   ` Tilman Schmidt
2009-09-20 21:13     ` Marcin Slusarz
2009-09-20 17:12   ` Alan Stern
2009-09-20 18:11     ` Greg KH [this message]
2009-09-21  1:59       ` Alan Stern
2009-09-21 23:03         ` Tilman Schmidt
2009-09-28 17:42         ` Status of Bug 8094 - ipaq oops on connecting "Vodafone VPA-II"? Matthias Geissert

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=20090920181133.GA14366@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tilman@imap.cc \
    /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.