From: Ismail Donmez <ismail@pardus.org.tr>
To: Len Brown <lenb@kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, Stelian Pop <stelian@popies.net>,
Andrea Gelmini <gelma@gelma.net>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: sonypc with Sony Vaio VGN-SZ1VP
Date: Wed, 27 Sep 2006 10:50:02 +0300 [thread overview]
Message-ID: <200609271050.03904.ismail@pardus.org.tr> (raw)
In-Reply-To: <200609270204.38970.len.brown@intel.com>
Hi,
27 Eyl 2006 Çar 09:04 tarihinde, Len Brown şunları yazmıştı:
[...]
> > > Will sony_acpi ever make it to the mainline? Its very useful for new
> > > Vaio models.
>
> Nope, not as it is. Useful != supportable.
>
> 1. It must not create any files under /proc/acpi
> This is creating a machine-specific API, which
> is exactly what we don't want Nobody can maintain
> 50 machine specific APIs.
>
> These objects must appear generic and under sysfs
> as if acpi were not involved in providing them.
>
> 2. its source code shall not live in drivers/acpi
> it is not part of the ACPI implementation after all --
> it is a platform specific driver.
Is there a such example code under kernel now, so one could look at it and fix
sony_acpi driver.
Regards,
ismail
--
They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety.
-- Benjamin Franklin
next prev parent reply other threads:[~2006-09-27 7:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 13:56 Andrea Gelmini
2006-09-26 16:29 ` Stelian Pop
2006-09-26 17:56 ` Ismail Donmez
2006-09-27 5:14 ` Andrew Morton
2006-09-27 5:59 ` Jan Engelhardt
2006-09-27 6:04 ` Len Brown
2006-09-27 7:50 ` Ismail Donmez [this message]
2006-09-28 15:48 ` Yu Luming
2006-09-27 16:26 ` Andrea Gelmini
2006-09-26 21:38 ` Andrea Gelmini
2006-09-27 11:51 stelian
2006-09-28 16:27 ` Yu Luming
2007-01-04 5:24 ` Len Brown
2007-01-04 10:09 ` Stelian Pop
2007-01-04 19:15 ` Mattia Dongili
2007-01-04 20:51 ` Andrew Morton
2007-01-04 21:18 ` Mattia Dongili
2007-01-04 21:28 ` Andrew Morton
2007-01-04 21:36 ` Timo Hoenig
2007-01-04 21:36 ` Richard Hughes
2007-01-04 21:58 ` Mattia Dongili
2007-01-05 17:02 ` Len Brown
2007-01-05 18:06 ` Mattia Dongili
2007-01-04 23:36 ` Stelian Pop
2007-01-04 23:44 ` Andrew Morton
2007-01-04 23:54 ` Stelian Pop
2007-01-05 4:16 ` Andrew Morton
2007-01-05 9:58 ` Stelian Pop
2007-01-05 2:20 ` MoRpHeUz
2007-01-05 0:11 ` Jan Engelhardt
2007-01-05 9:15 ` Mattia Dongili
2007-01-05 9:59 ` Stelian Pop
2007-01-04 23:34 ` Stelian Pop
2007-01-05 10:02 ` Stelian Pop
2007-01-05 12:13 ` Mattia Dongili
2007-01-05 14:23 ` Jan Engelhardt
2007-01-09 15:19 ` Luming Yu
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=200609271050.03904.ismail@pardus.org.tr \
--to=ismail@pardus.org.tr \
--cc=akpm@osdl.org \
--cc=gelma@gelma.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stelian@popies.net \
/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
Powered by JetHome