public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prisoner Of War <inmate@agf-team.net>
To: linux-kernel@vger.kernel.org
Subject: USB maintainer, Greg Kroah ---->> PWC discussion
Date: Sat, 30 Apr 2005 17:07:04 +0200	[thread overview]
Message-ID: <42739F18.8040502@agf-team.net> (raw)

Dear readers of this maillinglist,

I'm most of the time very happy that there is Linux (special thanks to 
Linus T.) and that i'm one happy computer user that isn't confronted all 
the time with a special blue screen.

I'm a user from the time kernel 2.0.xx started and yes it's not from the 
start but it's still a long time....

I'm almost very happy with the things that are going on in kernel land. 
And yes not all things that work in Wintendo aka Winboot will work under 
linux. But there are a few things that always worked very well. 
Including webcams. (yes i can stay polite and be nice but that won't 
have the effect i want....)

Now my dear daughter has her own laptop and she insists to run linux on 
it. She just had her birthday and she got a nice logitec webcam so she 
can use it on that very stable system.

BUT NO!!

These days she can't anymore. Why ?? Because there's a problem between 
hrh Greg Kroah (usb maintainer) and somebody who did his best to give 
user the possibility of using a goodworking webcam.

I don't want the discussion if it's proper or not to have that driver in 
the kernel. I have just the problem that i have todo more before it works...

I realy don't give a sh*t about that. I just want one thing and that is 
that the webcam starts working again and work like in ASAP. Rather 
yesterday then today.

So here's a user yrh Greg Kroah that realy wants that driver back in. 
I'm a user and i'm not alone! There are more users like me and what we 
want is that we have hardware which should work with the os we choose. 
We choose linux because it's stable and it's not wintendo. Are you gonna 
decide for us what we want ?? I hope not coz history tells us that those 
kind of people never last long...

So what about it are you going to help me? And make it possible for us 
to use our choosen hardware?


I realy hope you listen to me / us because I / we choose linux above 
windows...


Regards,

Gabriel Kenter




-=-=-
... He's turned his life around. He used to be depressed and miserable. 
Now he's miserable and depressed.
        -- David Frost
* TagZilla 0.057 * http://tagzilla.mozdev.org


-- 
This message was scanned for spam and viruses by BitDefender.
For more information please visit http://linux.bitdefender.com/



             reply	other threads:[~2005-04-30 15:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-30 15:07 Prisoner Of War [this message]
2005-04-30 16:17 ` USB maintainer, Greg Kroah ---->> PWC discussion Adrian Bunk
2005-04-30 16:30   ` Jesper Juhl
2005-04-30 19:09     ` Prisoner Of War
2005-04-30 19:19       ` Arjan van de Ven
2005-04-30 19:25         ` Prisoner Of War
2005-04-30 19:32       ` Al Viro
2005-05-01 10:19         ` Prisoner Of War
2005-05-01 17:16           ` Jose Luis Domingo Lopez
2005-05-02 18:11       ` Bill Davidsen
2005-04-30 19:19   ` Prisoner Of War

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=42739F18.8040502@agf-team.net \
    --to=inmate@agf-team.net \
    --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