public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Hanno Böck" <mail@hboeck.de>, "Andrew Morton" <akpm@osdl.org>,
	"Brown, Len" <len.brown@intel.com>,
	acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	"Karol Kozimor" <sziwan@hell.org.pl>,
	"Christian Aichinger" <Greek0@gmx.net>
Subject: Re: [ACPI] Re: asus_acpi still broken on Samsung P30/P35
Date: Wed, 21 Dec 2005 20:22:54 +0100	[thread overview]
Message-ID: <43A9AB8E.7010802@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0512211035370.4827@g5.osdl.org>

Linus Torvalds schrieb:
> 
> On Wed, 21 Dec 2005, Hanno Böck wrote:
> 
>>This is not "some minor issue", this completely breaks the usage of current 
>>vanilla-kernels on certain Hardware. Can please, please, please anyone in the 
>>position to do this take care that this patch get's accepted before 2.6.15?
>>
>>The patch is available inside mm-sources or here:
>>http://www.int21.de/samsung/p30-2.6.14.diff
>>
>>If I should send it to anyone else or if there's anything I can do to help 
>>fixing this, I'm glad to help.
> 
> 
> Last I saw this patch, I wrote this reply (the patch above is still 
> broken). Nobody ever came back to me on it.
> [...]

I've been busy trying to gather all the different DSDTs to compare
them and find out if the logic can be simplified. Will try to come
up with a patch addressing all your and Andrew's concerns until friday.

Regards,
Carl-Daniel

      reply	other threads:[~2005-12-21 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 15:11 asus_acpi still broken on Samsung P30/P35 Hanno Böck
2005-12-21 18:37 ` Linus Torvalds
2005-12-21 19:22   ` Carl-Daniel Hailfinger [this message]

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=43A9AB8E.7010802@gmx.net \
    --to=c-d.hailfinger.devel.2005@gmx.net \
    --cc=Greek0@gmx.net \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@hboeck.de \
    --cc=sziwan@hell.org.pl \
    --cc=torvalds@osdl.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