From: minyard@acm.org
To: qemu-devel@nongnu.org
Cc: "Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH v2 0/3] ipmi: Fix SEL get/set time commands
Date: Sun, 20 Aug 2017 16:46:39 -0500 [thread overview]
Message-ID: <1503265602-9349-1-git-send-email-minyard@acm.org> (raw)
Resend, with the style issues and the problem that Cédric pointed
out.
Thanks Cédric, for the review.
Changes from v1:
* Get the data from the proper offset in the command array.
* Use {} on all if statements.
next reply other threads:[~2017-08-20 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 21:46 minyard [this message]
2017-08-20 21:46 ` [Qemu-devel] [PATCH v2 1/3] ipmi: Fix SEL get/set time commands minyard
2017-08-21 7:28 ` Cédric Le Goater
2017-08-20 21:46 ` [Qemu-devel] [PATCH v2 2/3] ipmi: Don't set the timestamp on add events that don't have it minyard
2017-08-20 21:46 ` [Qemu-devel] [PATCH v2 3/3] ipmi: Add the platform event message command minyard
2017-08-20 22:24 ` Philippe Mathieu-Daudé
2017-08-20 22:41 ` Corey Minyard
2017-08-21 7:37 ` Cédric Le Goater
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=1503265602-9349-1-git-send-email-minyard@acm.org \
--to=minyard@acm.org \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--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).