From: Gene Heskett <gene.heskett@verizon.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] USB update for 2.4.22-pre5
Date: Thu, 17 Jul 2003 05:47:03 -0400 [thread overview]
Message-ID: <200307170547.03264.gene.heskett@verizon.net> (raw)
In-Reply-To: <20030717041037.GA4532@kroah.com>
On Thursday 17 July 2003 00:10, Greg KH wrote:
>On Wed, Jul 16, 2003 at 10:19:36PM -0400, Gene Heskett wrote:
>> So I repeat, something in that -pre5 to -pre6 patching of the usb
>> stuffs broke this. Possibly even this patchset below.
>
>If you just back out the usb patches in -pre6 does it help?
>
>There is only 1 patch in here that might possibly be in code that
> you are hitting, the change to drivers/usb/usb.c If you change
> that back, does it help?
I don't know, and likely won't try very soon as I just got back to the
house from putting my wife in the shop, complications from emphesima.
Long time 3 pack a day smoker, can't quit.
>I'd also really suggest asking the quick cam driver authors, as this
>driver isn't in the kernel tree so we have no idea what it could be
>doing.
My conversations with them haven't enlightened me, so I'm now waiting
on a phone call from the SunPlus folks to see if I can obtain any
data on the chipset in that camera, which is newer than what the
qcam-vc folks had when they wrote that.
>thanks,
>
>greg k-h
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
prev parent reply other threads:[~2003-07-17 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 17:08 [BK PATCH] USB update for 2.4.22-pre5 Greg KH
2003-07-17 2:19 ` Gene Heskett
[not found] ` <20030717041037.GA4532@kroah.com>
2003-07-17 9:47 ` Gene Heskett [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=200307170547.03264.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).