public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Ben Collins <ben.collins@ubuntu.com>
Cc: linux-kernel@vger.kernel.org, Eric Piel <eric.piel@tremplin-utc>
Subject: Re: [RFC] Include ACPI DSDT from INITRD patch into mainline
Date: Fri, 1 Dec 2006 21:55:51 +0000	[thread overview]
Message-ID: <20061201215551.66b6eb60@localhost.localdomain> (raw)
In-Reply-To: <1165006694.5257.968.camel@gullible>

> > Does that change the fact it is ugly ?
> 
> No, but it does beg the question "how else can it be done"?

Agreed.
 
> Distros need a way for users to add a fixed DSDT without recompiling
> their own kernels.

Legal rights to do so aside, do they ? and if they do does it have to be
an ugly hack in the mainstream kernel. 

Alan

  reply	other threads:[~2006-12-01 21:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01 18:36 [RFC] Include ACPI DSDT from INITRD patch into mainline Ben Collins
2006-12-01 18:56 ` Alan
2006-12-01 19:35   ` Ben Collins
2006-12-01 19:45     ` Arjan van de Ven
2006-12-01 21:01       ` Ben Collins
2006-12-01 21:49         ` Arjan van de Ven
2006-12-01 22:35           ` Ben Collins
2006-12-02  7:45             ` Arjan van de Ven
2006-12-04 10:58               ` Stefan Seyfried
2006-12-01 19:53     ` Alan
2006-12-01 20:58       ` Ben Collins
2006-12-01 21:55         ` Alan [this message]
2006-12-01 22:01           ` Arkadiusz Miskiewicz
2006-12-01 22:17             ` Alan
2006-12-02 10:28               ` Arjan van de Ven
2006-12-02 12:50             ` Acer smart battery (was Re: [RFC] Include ACPI DSDT from INITRD patch into mainline) Pavel Machek
2006-12-02 17:34               ` Arkadiusz Miskiewicz
2006-12-02 18:58                 ` Pavel Machek
2006-12-02  0:21         ` [RFC] Include ACPI DSDT from INITRD patch into mainline Dave Jones
2006-12-02 10:25           ` Arjan van de Ven
2006-12-02 10:30 ` Arjan van de Ven
2006-12-02 11:11   ` Jan Engelhardt
2006-12-02 16:15   ` Sergey Vlasov

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=20061201215551.66b6eb60@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=ben.collins@ubuntu.com \
    --cc=eric.piel@tremplin-utc \
    --cc=linux-kernel@vger.kernel.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