From: Rocky Craig <rocky.craig@hp.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "minyard@acm.org" <minyard@acm.org>,
ykzhao <yakui.zhao@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Myron Stowe <myron.stowe@hp.com>,
"openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>,
"lenb@kernel.org" <lenb@kernel.org>
Subject: Re: [Openipmi-developer] IPMI device discovery [was Re: [PATCH ] IPMI: Locate the IPMI system interface in ACPI namespace]
Date: Wed, 18 Nov 2009 14:53:38 -0700 [thread overview]
Message-ID: <4B046CE2.90200@hp.com> (raw)
In-Reply-To: <200911181419.27238.bjorn.helgaas@hp.com>
Bjorn Helgaas emitted:
> I disagree that this requirement was lost....
Sorry, my words did not convey my intended meaning, which was that
"conformance" or "coherence" was lost, with SPMI also being listed
in ACPI general namespace.
You actually stated this with greater clarity:
> There may be firmware that has an SPMI but neglects to put the device
> in the namespace.
That may be the case on some legacy servers.
Rocky
next prev parent reply other threads:[~2009-11-18 21:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 9:18 [PATCH ] IPMI: Locate the IPMI system interface in ACPI namespace yakui.zhao
2009-11-16 17:51 ` Bjorn Helgaas
2009-11-17 0:59 ` ykzhao
2009-11-17 14:59 ` Bjorn Helgaas
2009-11-18 3:41 ` ykzhao
2009-11-18 16:45 ` IPMI device discovery [was Re: [PATCH ] IPMI: Locate the IPMI system interface in ACPI namespace] Bjorn Helgaas
2009-11-18 20:40 ` [Openipmi-developer] " Rocky Craig
2009-11-18 21:19 ` Bjorn Helgaas
2009-11-18 21:53 ` Rocky Craig [this message]
2009-11-19 11:01 ` ykzhao
2009-11-30 23:46 ` Bela Lubkin
2009-11-19 11:09 ` ykzhao
2009-11-16 20:37 ` [Openipmi-developer] [PATCH ] IPMI: Locate the IPMI system interface in ACPI namespace Bela Lubkin
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=4B046CE2.90200@hp.com \
--to=rocky.craig@hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=minyard@acm.org \
--cc=myron.stowe@hp.com \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=yakui.zhao@intel.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