From: Paul Mackerras <paulus@samba.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, Corey Minyard <minyard@mvista.com>
Subject: Re: IPMI
Date: Tue, 14 Jan 2003 20:23:07 +1100 [thread overview]
Message-ID: <15907.55035.787654.77224@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20030114084011.6AB412C466@lists.samba.org>
Rusty Russell writes:
> Telling me what IPMI is, and why I might need it, would be a good
> thing... Please, Corey, I'm feeling generation-gapped by the
> acronyms...
There is a Documentation/IPMI.txt, which would serve as an excellent
example of how _not_ to write a documentation file, should you ever
decide to write a "Rusty's Unreliable Guide to Writing Kernel
Documentation" and need an example to pillory. I quote:
> The Linux IPMI Driver
> ---------------------
> Corey Minyard
> <minyard@mvista.com>
> <minyard@acm.org>
>
> This document describes how to use the IPMI driver for Linux. If you
> are not familiar with IPMI itself, see the web site at
> http://www.intel.com/design/servers/ipmi/index.htm. IPMI is a big
> subject and I can't cover it all here!
Maybe it can't all be covered here, but some basic explanation of what
IPMI is and does is essential, even if just so that people who don't
need IPMI can work that out.
Paul.
next prev parent reply other threads:[~2003-01-14 9:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 8:29 IPMI Rusty Russell
2003-01-14 9:23 ` Paul Mackerras [this message]
2003-01-14 11:55 ` IPMI Bruce Harada
2003-01-14 12:36 ` IPMI Arjan van de Ven
2003-01-14 13:07 ` IPMI Bruce Harada
2003-01-14 14:35 ` IPMI Corey Minyard
2003-01-15 3:36 ` IPMI Paul Mackerras
2003-01-15 3:55 ` IPMI Corey Minyard
2003-01-14 14:29 ` IPMI Corey Minyard
2003-01-14 14:46 ` IPMI Adrian Bunk
2003-01-14 14:59 ` IPMI Wichert Akkerman
2003-01-15 3:49 ` IPMI Rusty Russell
2003-01-15 20:46 ` IPMI Horst von Brand
2003-01-15 5:08 IPMI Perez-Gonzalez, Inaky
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=15907.55035.787654.77224@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@mvista.com \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome