public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Corey Minyard <cminyard@mvista.com>
Cc: linux-kernel@vger.kernel.org, Corey Minyard <minyard@mvista.com>
Subject: Re: IPMI
Date: Wed, 15 Jan 2003 14:49:55 +1100	[thread overview]
Message-ID: <20030115044228.C33A82C054@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 14 Jan 2003 08:29:33 MDT." <3E241ECD.6000108@mvista.com>

In message <3E241ECD.6000108@mvista.com> you write:
> Does this work, or would you like more detail?
> 
> config IPMI_HANDLER
>        tristate 'IPMI top-level message handler'
>        help
>          This enables the central IPMI message handler, required for IPMI
>          to work.  Note that you must have this enabled to enable any
>          other IPMI things.  IPMI is a standard for managing sensors
>          (temperature, voltage, etc.) in a system.  If you don't know
>          what it is, your system probably doesn't have it and you can
>          ignore this option.  See Documentation/IPMI.txt for more
>          details on the driver.

I don't mean to nitpick, but I want to know whether I need it or not.

Now, if I read this correctly, CONFIG_IPMI would be a more appropriate
name.  But changing the message at least would make it clearer:

	config IPMI_HANDLER
	       tristate 'IPMI support'

Now, the message.  How about this:
       help
	  Intelligent Peripheral Management Interface (IPMI) is a
	  standard for managing sensors (temperature, voltage, etc.)
	  in a system.  Most IA64 and x86 servers shipped since 2002
	  have support for it.  See Documentation/IPMI.txt for more
	  details.  Say "N" unless configuring for a recent x86 or
	  IA64 machine.

Tweak details to suit: maybe IPMI goes furthur back, maybe it's also
on desktops, maybe it's so widespread that the suggested default
should be "Y" for all IA64 and x86.

But the "what to do if you know nothing" is important: people who know
what IPMI is don't need the help message.

Hope that clarifies?
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  parent reply	other threads:[~2003-01-15  4:33 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 ` IPMI Paul Mackerras
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   ` Rusty Russell [this message]
2003-01-15 20:46     ` IPMI Horst von Brand
  -- strict thread matches above, loose matches on Subject: below --
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=20030115044228.C33A82C054@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=cminyard@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@mvista.com \
    /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