From: Corey Minyard <minyard@acm.org>
To: lkml <linux-kernel@vger.kernel.org>, Linus Torvalds <torvalds@osdl.org>
Subject: [PATCH] IPMI driver updates, part 1b
Date: Tue, 24 Feb 2004 07:55:04 -0600 [thread overview]
Message-ID: <403B57B8.2000008@acm.org> (raw)
It looks like part 1 of the IPMI driver updates was a little too big to
get through. So I've split it up. Part 1a and part1b must both be
applied. Here's the original message. Also, this is for the 2.6.3 kernel.
It has been far too long since the last IPMI driver updates, but now all
the planets have aligned and all the pieces I needed are in and all seem
to be working. This update is coming as four parts that must be applied
in order, but the later parts do not have to be applied for the former
parts to work.
This first part does basic updates to the IPMI infrastructure. It adds
support for messaging through an IPMI LAN interface, which is required
for some system software that already exists on other IPMI drivers. It
also does some renaming (in preparation for one of the later patches)
and a lot of little cleanups.
FYI, IPMI is a standard for monitoring and maintaining a system. It
provides interfaces for detecting sensors (voltage, temperature, etc.)
in the system and monitoring those sensors. Many systems have extended
capabilities that allow IPMI to control the system, doing things like
lighting leds and controlling hot-swap. This driver allows access to
the IPMI system.
-Corey
next reply other threads:[~2004-02-24 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 13:55 Corey Minyard [this message]
2004-02-24 23:51 ` [PATCH] IPMI driver updates, part 1b Corey Minyard
2004-02-25 1:00 ` Andrew Morton
2004-02-25 15:59 ` Corey Minyard
2004-02-25 20:02 ` Andrew Morton
2004-02-25 16:15 ` Corey Minyard
2004-02-25 20:05 ` Andrew Morton
2004-02-25 21:12 ` Corey Minyard
2004-02-25 20:32 ` Andrew Morton
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=403B57B8.2000008@acm.org \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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