From: Corey Minyard <tcminyard@gmail.com>
To: minyard@acm.org, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Eric Blake" <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] Small IPMI fixes
Date: Tue, 23 Jan 2018 10:55:15 -0600 [thread overview]
Message-ID: <09678455-2c70-ff07-7f2a-f4135e28e75f@gmail.com> (raw)
In-Reply-To: <1516064279-14816-1-git-send-email-minyard@acm.org>
Michael? Anyone? Can we get these in?
Thanks
-corey
On 01/15/2018 06:57 PM, minyard@acm.org wrote:
> These are some fixes I've had for a while (mostly). They are small
> fixes and additions for various things. It would be nice to be able
> to get these into the upcoming release.
>
> I also add myself as the maintainer for the IPMI code, since that
> seemed appropriate.
>
> Changes in v2:
>
> I removed the "other" fixes (the one to vl.c) from the previous patch
> set, these are all IPMI-related changes. I also moved adding myself
> as the IPMI maintainer to the first patch, per Marc-André.
>
next prev parent reply other threads:[~2018-01-23 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 0:57 [Qemu-devel] [PATCH v2] Small IPMI fixes minyard
2018-01-16 0:57 ` [Qemu-devel] [PATCH 1/7] Add maintainer for the IPMI code minyard
2018-01-16 0:57 ` [Qemu-devel] [PATCH 2/7] ipmi: Fix SEL get/set time commands minyard
2018-01-16 0:57 ` [Qemu-devel] [PATCH 3/7] ipmi: Don't set the timestamp on add events that don't have it minyard
2018-01-16 0:57 ` [Qemu-devel] [PATCH 4/7] ipmi: Add the platform event message command minyard
2018-01-16 0:57 ` [Qemu-devel] [PATCH 5/7] ipmi: Fix macro issues minyard
2018-01-16 0:57 ` [Qemu-devel] [PATCH 6/7] ipmi: disable IRQ and ATN on an external disconnect minyard
2018-01-16 0:57 ` [Qemu-devel] [PATCH 7/7] ipmi: Allow BMC device properties to be set minyard
2018-01-23 16:55 ` Corey Minyard [this message]
2018-01-31 17:52 ` [Qemu-devel] [PATCH v2] Small IPMI fixes Greg Kurz
2018-02-01 2:25 ` Michael S. Tsirkin
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=09678455-2c70-ff07-7f2a-f4135e28e75f@gmail.com \
--to=tcminyard@gmail.com \
--cc=clg@kaod.org \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=minyard@acm.org \
--cc=mst@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).