From: Greg KH <greg@kroah.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] USB changes for 2.5.53
Date: Sun, 29 Dec 2002 00:09:36 -0800 [thread overview]
Message-ID: <20021229080935.GA19453@kroah.com> (raw)
In-Reply-To: <20021228200120.79E3F10BA@oscar.casa.dyndns.org>
On Sat, Dec 28, 2002 at 03:01:19PM -0500, Ed Tomlinson wrote:
> Greg KH wrote:
>
> > Hi,
> >
> > Here's a lot of little USB changes, mostly all of them are conversions
> > to using the driver core model better for usb and usb-serial devices.
> >
> > Please pull from: bk://linuxusb.bkbits.net/linus-2.5
>
> Something in this seems to be ooping here:
Hm, I can't duplicate this myself here. My pl2303 device works just
fine, but it is one that doesn't need the "hack" to work properly. And
I didn't change any code in that area.
Can you duplicate this when you plug in your pl2303 device, after
booting? And can you enable CONFIG_KALLSYMS to get a better oops
message that might be more helpful?
thanks,
greg k-h
prev parent reply other threads:[~2002-12-29 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 7:59 [BK PATCH] USB changes for 2.5.53 Greg KH
2002-12-28 20:01 ` Ed Tomlinson
2002-12-29 8:09 ` Greg KH [this message]
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=20021229080935.GA19453@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox