From: Michael Ellerman <michael@ellerman.id.au>
To: Christian Krafft <krafft@de.ibm.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>,
Arnd Bergmann <arnd.bergmann@de.ibm.com>
Subject: Re: [patch] ipmi: check, if default ports are accessible on PPC
Date: Tue, 27 Feb 2007 11:27:10 +0900 [thread overview]
Message-ID: <1172543230.15967.47.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20070226160917.2c801ec7@localhost>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
On Mon, 2007-02-26 at 16:09 +0100, Christian Krafft wrote:
> Subject: ipmi: check, if default ports are accessible on PPC
>
> From: Christian Krafft <krafft@de.ibm.com>
>
> ipmi_si_intf tries to access default ports, if no device could
> be found elsewhere. On PPC we have a function to check,
> if these legacy IO ports are accessible. This patch adds
> a check for these ports on PPC.
> This patch fixes a breakage of IPMI module
> on PPC machines without a BMC.
>
> Signed-off-by: Christian Krafft <krafft@de.ibm.com>
Yep that fixes the problem on my machine.
Acked-by: Michael Ellerman <michael@ellerman.id.au>
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-27 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1172223703.4695.59.camel@concordia.ozlabs.ibm.com>
[not found] ` <20070223135859.62e19ca8@localhost>
[not found] ` <1172295412.16060.8.camel@concordia.ozlabs.ibm.com>
2007-02-26 15:09 ` [patch] ipmi: check, if default ports are accessible on PPC Christian Krafft
2007-02-27 2:27 ` Michael Ellerman [this message]
2007-04-20 17:48 ` Olaf Hering
2007-04-20 18:08 ` Olaf Hering
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=1172543230.15967.47.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=arnd.bergmann@de.ibm.com \
--cc=krafft@de.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).