From: Diego Calleja <diegocg@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: luca.risolia@studio.unibo.it, linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, gregkh@suse.de
Subject: Re: Oops with w9968cf
Date: Sat, 31 Dec 2005 20:48:45 +0100 [thread overview]
Message-ID: <20051231204845.313ac4c9.diegocg@gmail.com> (raw)
In-Reply-To: <20051231143229.GI3811@stusta.de>
El Sat, 31 Dec 2005 15:32:29 +0100,
Adrian Bunk <bunk@stusta.de> escribió:
> Hi Diego,
>
> thanks for your report.
>
> Is this issue still present in kernel 2.6.15-rc7?
> Which was the last working kernel?
I've found it's not easily reproducible - I tried to reproduce
again and I couldn't. I've not used my webcam a lot and it's
easy to use it without getting oopses so I have no idea of
since when this bug has been there. I though it was a
w9968 - which is why I CC'ed luca risolia (the maintainer)
I'll try to reproduce it again.
prev parent reply other threads:[~2005-12-31 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 14:18 Oops with w9968cf Diego Calleja
2005-12-31 14:32 ` Adrian Bunk
2005-12-31 19:48 ` Diego Calleja [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=20051231204845.313ac4c9.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=luca.risolia@studio.unibo.it \
/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