public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "P. Christeas" <p_christ-U04EIuiosng@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: Need for an ACPI webpage
Date: Fri, 18 Oct 2002 17:25:42 +0300	[thread overview]
Message-ID: <200210181725.42975.p_christ@hol.gr> (raw)
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD0236DF31-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>

> Look at blacklist.c.
>
> Should we add these to that table?
 Perhaps

>
> The code is the only thing that is guaranteed to be up to date. I think it
> would be nice to have a more readable version of that list online, but it
> will quickly become outdated unless someone actively maintains it (you?) or
> it is auto-generated from the source.
>
> Regards -- Andy

The code itself may not be the best place for a newbie to look at. What about 
things that are already covered by an old ver or things that have been proven 
to fail? A second reason is that we could not practically have many patch 
DSDT's in our kernel (or can we?).
I wouldn't mind being one of the mainteners of the list, but I don't have much 
webspace for that. The best way could be to use this list (acpi-devel) to 
post requests like 'could you add the line "x-brand 2.5.x blah blah" to the 
table?' so that the maintener won't do much himself. Testing can not be done 
by one person, anyway.
One more way that the table won't get outdated is if we put it on an 
'official' server (like yours). This way readers will harass us about wrong 
entries.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2002-10-18 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 21:41 Need for an ACPI webpage Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD0236DF31-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-10-17 21:57   ` Andrew Kohlsmith
2002-10-18 14:25   ` P. Christeas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-18 16:55 Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD0236DF37-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-10-18 20:39   ` P. Christeas
     [not found]     ` <200210182339.37324.p_christ-U04EIuiosng@public.gmane.org>
2002-10-18 20:49       ` Andrew Kohlsmith
2002-10-17 21:20 P. Christeas

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=200210181725.42975.p_christ@hol.gr \
    --to=p_christ-u04eiuiosng@public.gmane.org \
    --cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
    --cc=andrew.grover-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