From: Myron Stowe <myron.stowe@hp.com>
To: minyard@acm.org
Cc: yakui.zhao@intel.com, linux-acpi@vger.kernel.org,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, lenb@kernel.org
Subject: [PATCH v2 0/3] ipmi: discovery precedence and update core driver with dev_printk
Date: Sat, 13 Mar 2010 11:13:37 -0700 [thread overview]
Message-ID: <20100313180121.20614.92547.stgit@bob.kio> (raw)
These patches change the precedence of PNP based discovery mechanisms
and update the driver's core to use dev_printk() and its constructs.
As part of this patch series I wanted to remove the 'PFX' argument from
ipmi_of_probe()'s dev_printk constructs as I believe it produces redundant
output but I do not have a PPC platform to test against.
---
v2 - I dropped the contentious attempt to remove the ACPI SPMI static
table as a discovery mechanism.
Myron Stowe (3):
ipmi: Raise precedence of PNP based discovery mechanisms (ACPI, PCI)
ipmi: Convert tracking of the ACPI device pointer to a PNP device
ipmi: Update driver to use 'dev_printk()' and its constructs
Corey: If you encounter any issues applying this series let me know,
including your current basis, and I'll re-work the series.
drivers/char/ipmi/ipmi_msghandler.c | 11 +-
drivers/char/ipmi/ipmi_si_intf.c | 205 ++++++++++++++++-------------------
2 files changed, 96 insertions(+), 120 deletions(-)
next reply other threads:[~2010-03-13 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 18:13 Myron Stowe [this message]
2010-03-13 18:13 ` [PATCH v2 1/3] ipmi: Raise precedence of PNP based discovery mechanisms (ACPI, PCI) Myron Stowe
2010-03-15 1:48 ` ykzhao
2010-03-16 15:03 ` Myron Stowe
2010-03-13 18:13 ` [PATCH v2 2/3] ipmi: Convert tracking of the ACPI device pointer to a PNP device Myron Stowe
2010-03-15 1:50 ` ykzhao
2010-03-13 18:13 ` [PATCH v2 3/3] ipmi: Update driver to use 'dev_printk()' and its constructs Myron Stowe
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=20100313180121.20614.92547.stgit@bob.kio \
--to=myron.stowe@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--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