From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'Greg KH'" <greg@kroah.com>,
"KOCHI, Takayoshi" <t-kouchi@mvf.biglobe.ne.jp>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
"Lee, Jung-Ik" <jung-ik.lee@intel.com>,
linux-kernel@vger.kernel.org
Subject: RE: bare pci configuration access functions ?
Date: Thu, 31 Oct 2002 18:07:31 -0800 [thread overview]
Message-ID: <EDC461A30AC4D511ADE10002A5072CAD04C7A495@orsmsx119.jf.intel.com> (raw)
> From: Greg KH [mailto:greg@kroah.com]
> Nice, thanks for pointing that out. But what about the fact that I
> think we can now start optimizing certain parts of the
> "generic" code to
> play nicer with Linux?
It is much much more important that ACPI be *correct* than fast or small. To
that end, it is better to not fork ACPI-Linux from ACPI-everyone else. Linux
benefits from core bugs found by other OSes (FBSD is not the only one - for
some reason I'm not allowed to mention who else is using ACPI CA but they
*do* send bug reports) and vice versa.
> Now I don't mean this to be an ACPI rant, I know why they did
> their code
> this way, and without it, there probably would not be any ACPI Linux
> code. I just don't think it's the best way (from an engineering
> standpoint) to do things. And again, we are getting way off
> topic from
> the original problem, sorry.
I'm used to ACPI ranting from all quarters, you know that ;-) but let me
just say this:
- ACPI is not performance-critical
- ACPI will never be simple and elegant, even if you made it Linux-specific
- Portability enhances correctness and maximizes developer productivity
- Read my lips, no new taxes!
(dunno where that last one came from ;-)
Regards -- Andy
next reply other threads:[~2002-11-01 2:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 2:07 Grover, Andrew [this message]
2002-11-01 2:45 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 22:00 Grover, Andrew
2002-10-31 22:11 ` Greg KH
2002-10-31 22:50 ` Scott Murray
2002-10-31 23:46 ` Greg KH
2002-11-01 0:23 ` Scott Murray
2002-10-31 23:37 ` KOCHI, Takayoshi
2002-10-31 23:54 ` Greg KH
2002-11-01 0:23 ` KOCHI, Takayoshi
2002-11-01 1:13 ` Greg KH
2002-10-31 21:07 Grover, Andrew
2002-10-31 21:23 ` Greg KH
2002-10-31 23:40 ` Kai Germaschewski
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=EDC461A30AC4D511ADE10002A5072CAD04C7A495@orsmsx119.jf.intel.com \
--to=andrew.grover@intel.com \
--cc=greg@kroah.com \
--cc=jung-ik.lee@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=t-kouchi@mvf.biglobe.ne.jp \
/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
all inboxes | Powered by JetHome®