public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <cminyard@mvista.com>
To: Adrian Bunk <bunk@fs.tum.de>, Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.5 patch] fix ipmi_devintf.c compilation
Date: Wed, 26 Mar 2003 08:36:47 -0600	[thread overview]
Message-ID: <3E81BAFF.7060002@mvista.com> (raw)
In-Reply-To: <20030326124523.GO24744@fs.tum.de>

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

Thank you for the quick heads-up.

Linus, I have attached a patch (with some documentation updates and 
another minor fix, too).  Please apply for the next release.

Thanks,

-Corey

Adrian Bunk wrote:

>On Mon, Mar 24, 2003 at 03:26:47PM -0800, Linus Torvalds wrote:
>  
>
>>...
>>Summary of changes from v2.5.65 to v2.5.66
>>============================================
>>...
>>Christoph Hellwig <hch@sgi.com>:
>>...
>>  o misc devfs_register cleanups
>>...
>>    
>>
>
>
>  
>


[-- Attachment #2: linux-ipmi-2.5.66-fix.diff --]
[-- Type: text/plain, Size: 2853 bytes --]

diff -urN linux.orig/Documentation/IPMI.txt linux-main/Documentation/IPMI.txt
--- linux.orig/Documentation/IPMI.txt	Tue Jan 14 11:16:08 2003
+++ linux-main/Documentation/IPMI.txt	Wed Mar 26 08:05:10 2003
@@ -5,6 +5,18 @@
 			  <minyard@mvista.com>
 			    <minyard@acm.org>
 
+The Intelligent Platform Management Interface, or IPMI, is a
+standard for controlling intelligent devices that monitor a system.
+It provides for dynamic discovery of sensors in the system and the
+ability to monitor the sensors and be informed when the sensor's
+values change or go outside certain boundaries.  It also has a
+standardized database for field-replacable units (FRUs) and a watchdog
+timer.
+
+To use this, you need an interface to an IPMI controller in your
+system (called a Baseboard Management Controller, or BMC) and
+management software that can use the IPMI system.
+
 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
diff -urN linux.orig/drivers/char/ipmi/Kconfig linux-main/drivers/char/ipmi/Kconfig
--- linux.orig/drivers/char/ipmi/Kconfig	Tue Jan 14 11:16:10 2003
+++ linux-main/drivers/char/ipmi/Kconfig	Wed Mar 26 08:05:10 2003
@@ -7,8 +7,14 @@
        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 do any other IPMI
-	 things.  See IPMI.txt for more details.
+	 to work.
+
+         IPMI is a standard for managing sensors (temperature,
+         voltage, etc.) in a system.
+
+         See Documentation/IPMI.txt for more details on the driver.
+
+	 If unsure, say N.
 
 config IPMI_PANIC_EVENT
        bool 'Generate a panic event to all BMCs on a panic'
diff -urN linux.orig/drivers/char/ipmi/ipmi_devintf.c linux-main/drivers/char/ipmi/ipmi_devintf.c
--- linux.orig/drivers/char/ipmi/ipmi_devintf.c	Wed Mar 26 08:00:57 2003
+++ linux-main/drivers/char/ipmi/ipmi_devintf.c	Wed Mar 26 08:13:31 2003
@@ -449,7 +449,7 @@
 	if (if_num > MAX_DEVICES)
 		return;
 
-	snprinf(name, sizeof(name), "ipmidev/%d", if_num);
+	snprintf(name, sizeof(name), "ipmidev/%d", if_num);
 
 	handles[if_num] = devfs_register(NULL, name, DEVFS_FL_NONE,
 					 ipmi_major, if_num,
diff -urN linux.orig/drivers/char/ipmi/ipmi_kcs_intf.c linux-main/drivers/char/ipmi/ipmi_kcs_intf.c
--- linux.orig/drivers/char/ipmi/ipmi_kcs_intf.c	Fri Feb 28 16:03:18 2003
+++ linux-main/drivers/char/ipmi/ipmi_kcs_intf.c	Wed Mar 26 08:14:11 2003
@@ -826,7 +826,7 @@
 	if (kcs_port && kcs_physaddr)
 		return -EINVAL;
 
-	new_kcs = kmalloc(kcs_size(), GFP_KERNEL);
+	new_kcs = kmalloc(sizeof(*new_kcs), GFP_KERNEL);
 	if (!new_kcs) {
 		printk(KERN_ERR "ipmi_kcs: out of memory\n");
 		return -ENOMEM;

      reply	other threads:[~2003-03-26 14:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 23:26 Linux 2.5.66 Linus Torvalds
2003-03-24 23:35 ` Larry McVoy
2003-03-25  0:14 ` Florin Iucha
2003-03-25  8:05   ` Rolf Eike Beer
2003-03-25  8:29     ` Marco Roeland
2003-03-25  0:16 ` Jeremy Brown
2003-03-25  0:22 ` Udo A. Steinberg
2003-03-25  0:30   ` Greg KH
2003-03-25  1:18     ` Udo A. Steinberg
2003-03-25  1:47       ` Greg KH
2003-03-25  4:18     ` CaT
2003-03-25  4:34       ` Greg KH
2003-03-25  5:56         ` CaT
2003-03-25  6:51           ` Greg KH
2003-03-25  7:22             ` CaT
2003-03-25  7:27               ` Greg KH
2003-03-25  0:53 ` John Cherry
2003-03-25  1:55 ` [REPRODUCABLE BUGS] " Toplica Tanaskovic
2003-03-25  3:19   ` James Simmons
2003-03-25  9:51     ` Toplica Tanaskovic
2003-03-26 20:24       ` James Simmons
2003-03-26 23:49         ` Torrey Hoffman
2003-03-27  0:20           ` James Simmons
2003-03-27  2:27             ` Joshua Kwan
2003-04-02 22:16               ` James Simmons
2003-04-03  1:02                 ` Joshua Kwan
2003-04-03  3:59                   ` James Simmons
2003-03-27 16:05         ` Toplica Tanaskovic
2003-03-26  2:53 ` Paweł Gołaszewski
2003-03-26  3:33   ` James Simmons
2003-03-26 11:00 ` [2.5 patch] fix sound/oss/mad16.c compile Adrian Bunk
2003-03-26 11:26 ` 2.5.66: compile problem with snd-ice1724 Adrian Bunk
2003-03-26 12:45 ` [2.5 patch] fix ipmi_devintf.c compilation Adrian Bunk
2003-03-26 14:36   ` Corey Minyard [this message]

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=3E81BAFF.7060002@mvista.com \
    --to=cminyard@mvista.com \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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