public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI Extensions for Display Adapters
Date: Sat, 24 Jan 2004 01:16:43 +0100	[thread overview]
Message-ID: <20040124001643.GL25416@poupinou.org> (raw)
In-Reply-To: <20040123234459.GB18100-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>

On Sat, Jan 24, 2004 at 12:44:59AM +0100, Karol Kozimor wrote:
> Thus wrote Ducrot Bruno:
> > On Fri, Jan 23, 2004 at 05:35:00PM -0500, Brown, Len wrote:
> > > Volunteers?
> > 
> > This is perhaps time to add some attribute to sysfs?
> 
> BTW: did anybody actually think of moving the Linux-specific bits to sysfs?
> I guess killing /proc/acpi would be a 2.7-thing though.
> Best regards,

Sometimes, I'm thinking about, but well, never got time to do it (it's
not in my priority list)...

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  parent reply	other threads:[~2004-01-24  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 22:35 ACPI Extensions for Display Adapters Brown, Len
     [not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8A41-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-01-23 23:13   ` Ducrot Bruno
     [not found]     ` <20040123231334.GJ25416-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-01-23 23:44       ` Karol Kozimor
     [not found]         ` <20040123234459.GB18100-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-24  0:16           ` Ducrot Bruno [this message]
2004-01-24 21:54   ` John Belmonte

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=20040124001643.GL25416@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@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