From: minyard@acm.org
To: Igor Mammedov <imammedo@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, minyard@acm.org, cminyard@mvista.com
Subject: [Qemu-devel] [PATCH v2 0/7] An IPMI over SMBus device
Date: Wed, 1 Jun 2016 11:26:53 -0500 [thread overview]
Message-ID: <1464798420-12018-1-git-send-email-minyard@acm.org> (raw)
This set of patches requires the previous IPMI ACPI patches, at least
starting with patch 4.
This set of patches fixes some fairly significant bugs with the
pm_smbus device, which basically just wasn't functional beyond
some very basic things. It's close to a rewrite of the state
machine.
After that, it adds an IPMI device on the SMBus.
Then it cleans up a few small things in the IPMI ACPI handling
that were SMBus specific, and adds the SMBus itself to the
ACPI tables. This required adding a 2.7 machine, though I've
seen a patch for that on the mailing list it has not been
added to the main repository yet.
-corey
next reply other threads:[~2016-06-01 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 16:26 minyard [this message]
2016-06-01 16:26 ` [Qemu-devel] [PATCH v2 1/7] i2c: Fix the PM SMBus driver so it actually works correctly minyard
2016-06-01 16:26 ` [Qemu-devel] [PATCH v2 2/7] pm_smbus: Add the ability to force block transfer enable minyard
2016-06-01 16:26 ` [Qemu-devel] [PATCH v2 3/7] ipmi: Add an SMBus IPMI interface minyard
2016-06-01 16:26 ` [Qemu-devel] [PATCH v2 4/7] acpi: Add i2c serial bus CRS handling minyard
2016-06-01 16:26 ` [Qemu-devel] [PATCH v2 5/7] ipmi: Fix SSIF ACPI handling to use the right CRS minyard
2016-06-01 16:26 ` [Qemu-devel] [PATCH v2 6/7] pc: Add 2.7 machine options minyard
2016-06-01 16:27 ` [Qemu-devel] [PATCH v2 7/7] pc: Add an SMB0 ACPI device to q35 minyard
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=1464798420-12018-1-git-send-email-minyard@acm.org \
--to=minyard@acm.org \
--cc=cminyard@mvista.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).