From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org,
'Jan Rychter' <jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.org>
Subject: Re: making progress with ACPI was: ACPI small patch update (20021024)
Date: Wed, 16 Jan 2002 14:53:21 -0500 [thread overview]
Message-ID: <20020116195314.GD2947@zaurus> (raw)
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD04C7A476-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
Hi!
> The real problem is there need to be more people fixing bugs. If you see a
> bug on your hardware, *you* are in the best spot to fix it. That is the only
> way this is going to work, long-term. You are asking for both a greater
> focus on the project's infrastructure, *and* more bug fixing, and that is
> only going to happen if people who have not previously pitched in, start
> doing so.
>
> It has been a rough road sometimes, but we (Intel) have tried to encourage
> community involvement as much as possible. But, I look over at the Linux USB
> list and see a much greater level of community contribution. We have some,
> but we need MORE. Without that involvement, we will get there with ACPI --
> it will just take longer.
USB is very different -- there are developers
with their own drivers that are on the list. Also
Linux-USB is older project. ACPI has just one
developer similar to usb developers -- the
person developing toshiba.c...
I do not think you being from intel is the problem...
Pavel
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
next prev parent reply other threads:[~2002-01-16 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 19:20 making progress with ACPI was: ACPI small patch update (20021024) Grover, Andrew
[not found] ` <EDC461A30AC4D511ADE10002A5072CAD04C7A476-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-01-16 19:53 ` Pavel Machek [this message]
2002-10-28 19:56 ` Alan Cox
2002-10-29 2:30 ` J
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 20:02 Nakajima, Jun
2002-10-28 20:31 joerg.beyer-htSm2yLGOjU
[not found] ` <200210282031.g9SKVAX06731-pb599fR3TxVkExQqqHjIK3sFFmKitW5W@public.gmane.org>
2002-10-28 21:16 ` Martin Waitz
[not found] ` <20021028211603.GD1402-4e/A4rHm86X2JYTphGNI2Q@public.gmane.org>
2002-10-28 21:34 ` Matthew Wilcox
2002-10-29 12:20 ` Derek Broughton
[not found] ` <005401c27f45$967de820$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org>
2002-10-29 14:02 ` Matthew Wilcox
[not found] ` <20021028213404.U27461-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2002-10-29 12:43 ` Aaron Gaudio
[not found] ` <20021029124329.GA25692-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org>
2002-10-29 14:03 ` Matthew Wilcox
2002-10-28 21:38 ` kneumann-4bfl1RV3iZDOEhgYWvzSCYQuADTiUCJX
2002-10-29 7:30 Jens Haug
[not found] ` <200210290730.g9T7UDD26513-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-10-29 10:45 ` Mark Pritchard
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=20020116195314.GD2947@zaurus \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.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