From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Theodore Tso <tytso@MIT.EDU>, Thomas Renninger <trenn@suse.de>,
Len Brown <lenb@kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
"Starikovskiy, Alexey Y" <aystarik@gmail.com>
Subject: Re: Kernel Version specific vendor override possibilities needed - Revert and provide osi=linux or provide a replacement
Date: Thu, 21 Feb 2008 12:50:35 -0300 [thread overview]
Message-ID: <20080221155035.GA5859@khazad-dum.debian.net> (raw)
In-Reply-To: <20080221143052.GA8389@srcf.ucam.org>
On Thu, 21 Feb 2008, Matthew Garrett wrote:
> My concern with this is that until we know where we deviate from the
> Windows behaviour, we don't know what strings we'd need to provide. And
> once we *do* know where we deviate, we should fix that deviation rather
> than provide an identifying string.
IMO we should "fix" deviations *only* when it makes sense to do so (I bet at
least one of the deviations we are going to find will be so hideously wrong
and ugly when compared to the Right Thing, that we will be at a very
unconfortable position if we need to implement it).
We better reserve judgment of what deviations we should be fixing or not for
when we find them in the first place.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2008-02-21 15:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 1:44 Kernel Version specific vendor override possibilities needed - Revert and provide osi=linux or provide a replacement Thomas Renninger
2008-02-20 10:31 ` Tomas Carnecky
2008-02-20 13:14 ` Henrique de Moraes Holschuh
2008-02-20 15:31 ` Thomas Renninger
2008-02-20 17:32 ` Matthew Garrett
2008-02-20 18:21 ` Thomas Renninger
2008-02-20 18:46 ` Matthew Garrett
2008-02-20 18:23 ` Henrique de Moraes Holschuh
2008-02-20 18:49 ` Matthew Garrett
2008-02-21 3:13 ` Henrique de Moraes Holschuh
2008-02-21 5:31 ` Sergio Monteiro Basto
2008-02-21 15:55 ` Henrique de Moraes Holschuh
2008-02-21 9:15 ` Matthew Garrett
2008-02-21 13:51 ` Theodore Tso
2008-02-21 14:30 ` Matthew Garrett
2008-02-21 14:48 ` Alexey Starikovskiy
2008-02-21 14:55 ` Matthew Garrett
2008-02-21 15:07 ` Alexey Starikovskiy
2008-02-21 15:50 ` Henrique de Moraes Holschuh [this message]
2008-02-26 16:26 ` Thomas Renninger
2008-02-26 16:31 ` Matthew Garrett
2008-02-22 14:07 ` Thomas Renninger
2008-02-22 18:10 ` Matthew Garrett
2008-02-26 16:26 ` Thomas Renninger
2008-02-21 8:41 ` Len Brown
2008-02-21 15:41 ` Thomas Renninger
2008-02-21 15:58 ` Matthew Garrett
2008-02-21 17:15 ` Theodore Tso
2008-02-22 23:36 ` Len Brown
2008-02-23 0:06 ` Len Brown
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=20080221155035.GA5859@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=aystarik@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=trenn@suse.de \
--cc=tytso@MIT.EDU \
/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