From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Chris Austen <austenc@us.ibm.com>,
openbmc@lists.ozlabs.org, Gus Schlachter <gussch@us.ibm.com>,
Russel L Young <youngr1@us.ibm.com>
Subject: Re: Event Log parser
Date: Tue, 22 Mar 2016 16:25:21 +1100 [thread overview]
Message-ID: <8760wfytha.fsf@birb.au.ibm.com> (raw)
In-Reply-To: <201603220522.u2M5Mn0f014732@d01av04.pok.ibm.com>
Chris Austen <austenc@us.ibm.com> writes:
> Here's a first pass at the event log parser. It has the stuff for the
> BMC viewer, the eSEL for (not sure really) and the Debug Data is a
> good old fashion PEL. Thoughts?
Using opal-elog-parse to parse the PEL?
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2016-03-22 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 5:22 Event Log parser Chris Austen
2016-03-22 5:25 ` Stewart Smith [this message]
2016-05-20 18:26 ` Vasant Hegde
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=8760wfytha.fsf@birb.au.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=austenc@us.ibm.com \
--cc=gussch@us.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=youngr1@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.