public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Timo Hoenig <thoenig-l3A5Bk7waGM@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
Subject: Re: [PATCH] Panasonic ACPI driver
Date: 15 Feb 2005 10:05:25 -0500	[thread overview]
Message-ID: <1108479925.2098.35.camel@d845pe> (raw)
In-Reply-To: <1108066047.32630.5.camel-dCxI//HcOdFeoWH0uzbU5w@public.gmane.org>

We should not include this driver in the kernel.

Rather than adding additional platform-specific drivers,
we should be migrating away from those that we already have
to simpler generic drivers for video and hot-keys -- where
the platform-dependent (naming) is done in user-space where
it is more extensible and supportable.

We've already got video.c, and I believe that we should start
to migrate to something like Luming's hot-key driver (see
earlier acpi-devel posts) in 2.6.12.

If a platform has some unique feature that no other platform
in the world has, then that justifies a platform specific driver
for that unique feature.  But for the common features, the
community will be better served by the simpler generic kernel
drivers that work on more systems.

thanks,
-Len




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-02-15 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 20:07 [PATCH] Panasonic ACPI driver Timo Hoenig
     [not found] ` <1108066047.32630.5.camel-dCxI//HcOdFeoWH0uzbU5w@public.gmane.org>
2005-02-15 15:05   ` Len Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-15  6:03 Yu, Luming
2005-03-15  8:53 ` Timo Hoenig

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=1108479925.2098.35.camel@d845pe \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=akpm-3NddpPZAyC0@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thoenig-l3A5Bk7waGM@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