Duncan SANDS wrote:
Thanks for your vote of confidence!
As I said, the final vote comes from the linux-usb project leaders. They
will have to work with you :)
I am glad someone is willing to take it over. It was just a play thingie
when I started it, but now it reminds me too strongly of a d
> >Dear Johan, I am sorry to hear that you will no longer be maintaining the
>speedtouch driver. It may have been your
> >first linux kernel driver, and it may have had a few bugs, but it has done good
>service to me and others. I am willing
> >to try and maintain the driver. While I don't hav
Duncan SANDS wrote:
Dear Johan, I am sorry to hear that you will no longer be maintaining the speedtouch driver. It may have been your
first linux kernel driver, and it may have had a few bugs, but it has done good service to me and others. I am willing
to try and maintain the driver. While I
> First of all thank you for getting this driver in the kernel and getting it looked
>over for bugs. The code is about two and a
> half years with no changes in the last 1.5 or two years or so. Judging by the bugs
>found, it doesn't seem too bad for my
> first linux kernel driver :) I tried to
Oliver Neukum wrote:
Am Mittwoch, 18. Dezember 2002 06:19 schrieb Duncan SANDS:
Hi Oliver, I think the driver should really be converted to using a
workqueue instead.
If it were a new driver of course.
But the current approach works in principle. As I am not the driver's
maintainer, I jus
Am Mittwoch, 18. Dezember 2002 06:19 schrieb Duncan SANDS:
> > Hi,
> >
> > this makes sure that the kernel thread is dead and gone on module unload.
> >
> > Regards
> > Oliver
>
> Hi Oliver, I think the driver should really be converted to using a
> workqueue instead.
If it were a
> Hi,
>
> this makes sure that the kernel thread is dead and gone on module unload.
>
> Regards
> Oliver
Hi Oliver, I think the driver should really be converted to using a workqueue
instead.
All the best,
Duncan.
---
Thi
Hi,
this makes sure that the kernel thread is dead and gone on module unload.
Regards
Oliver
You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.
==
