From: "Tanous, Ed" <ed.tanous@intel.com>
To: chunhui.jia <chunhui.jia@linux.intel.com>,
Patrick Venture <venture@google.com>
Cc: "Wang, Kuiying" <kuiying.wang@intel.com>,
"Mihm, James" <james.mihm@intel.com>,
"Nguyen, Hai V" <hai.v.nguyen@intel.com>,
"Feist, James" <james.feist@intel.com>,
"Jia, Chunhui" <chunhui.jia@intel.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
"Li, Yong B" <yong.b.li@intel.com>,
"Yang, Cheng C" <cheng.c.yang@intel.com>,
Brad Bishop <bradleyb@fuzziesquirrel.com>,
"Xu, Qiang" <qiang.xu@intel.com>,
"kun.yi.731@gmail.com" <kun.yi.731@gmail.com>,
"geissonator@yahoo.com" <geissonator@yahoo.com>
Subject: RE: RE: Proposal for caching/buffering POST codes list for one boot process.
Date: Mon, 27 Aug 2018 15:45:53 +0000 [thread overview]
Message-ID: <7E9441B1E5EFFD4681F54958E821699345835CCF@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <2018082715593358738018@linux.intel.com>
> Could you confirm if the "/xyz/openbmc_project/host/post/1" that we talked here contains a list of post code for one cycle?
Correct. Each one would contain a list of POST codes for that boot.
-Ed
next prev parent reply other threads:[~2018-08-27 15:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 7:28 Proposal for caching/buffering POST codes list for one boot process Wang, Kuiying
2018-08-24 16:12 ` Tanous, Ed
2018-08-24 18:07 ` Patrick Venture
2018-08-24 19:33 ` Tanous, Ed
2018-08-27 7:59 ` chunhui.jia
2018-08-27 15:45 ` Tanous, Ed [this message]
2018-08-27 23:52 ` Kun Yi
2018-08-27 23:55 ` Kun Yi
2018-08-27 23:58 ` Kun Yi
2018-08-28 6:09 ` Tanous, Ed
2018-08-29 4:44 ` Wang, Kuiying
2018-08-29 12:19 ` Brad Bishop
2018-08-30 7:23 ` Wang, Kuiying
2018-09-04 20:12 ` Brad Bishop
2018-09-05 7:25 ` Wang, Kuiying
2018-09-05 12:17 ` Brad Bishop
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=7E9441B1E5EFFD4681F54958E821699345835CCF@ORSMSX114.amr.corp.intel.com \
--to=ed.tanous@intel.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=cheng.c.yang@intel.com \
--cc=chunhui.jia@intel.com \
--cc=chunhui.jia@linux.intel.com \
--cc=geissonator@yahoo.com \
--cc=hai.v.nguyen@intel.com \
--cc=james.feist@intel.com \
--cc=james.mihm@intel.com \
--cc=kuiying.wang@intel.com \
--cc=kun.yi.731@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=qiang.xu@intel.com \
--cc=venture@google.com \
--cc=yong.b.li@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 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.