From: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
To: trenn@suse.de
Cc: linux-acpi@vger.kernel.org, "Brown, Len" <len.brown@intel.com>,
acpi4asus-user@lists.sourceforge.net
Subject: Re: [PATCH] Repost: asus strict model checking
Date: Tue, 01 Aug 2006 21:44:11 +0400 [thread overview]
Message-ID: <44CF92EB.4010801@linux.intel.com> (raw)
In-Reply-To: <1154452931.4302.407.camel@queen.suse.de>
Thomas Renninger wrote:
> On Tue, 2006-08-01 at 20:11 +0400, Alexey Starikovskiy wrote:
>> Checks for Samsung P30/P35 are real hacks IMHO.
> Why?
Because this DSDT signature could appear on any machine, and has nothing to do
with ASUS or Samsung.
next prev parent reply other threads:[~2006-08-01 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 13:15 [PATCH] Repost: asus strict model checking Thomas Renninger
2006-08-01 13:58 ` Alexey Starikovskiy
2006-08-01 15:29 ` Thomas Renninger
2006-08-01 16:11 ` Alexey Starikovskiy
2006-08-01 17:22 ` Thomas Renninger
2006-08-01 17:44 ` Alexey Starikovskiy [this message]
2006-08-02 10:00 ` Thomas Renninger
2006-08-02 18:49 ` Alexey Starikovskiy
2006-08-03 8:40 ` Thomas Renninger
2006-08-02 16:00 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2006-08-02 20:12 Brown, Len
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=44CF92EB.4010801@linux.intel.com \
--to=alexey_y_starikovskiy@linux.intel.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=trenn@suse.de \
/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