From: Patrick Venture <venture@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: inband bmc firmware upload
Date: Mon, 9 Jul 2018 08:19:49 -0700 [thread overview]
Message-ID: <CAO=notwagKYN0XT4F3TU8EZntYUiQ0Z+wNzvhV9C6NnqSsDO2w@mail.gmail.com> (raw)
I'm going to restage the IPMI OEM handler for review for only using
the IPMI Block transfer interface, and try to get our internal tool
compiling in the open world for only that interface. Then once it's
reviewed, etc, I can push out the PCI and LPC interfaces.
Sounds reasonable?
Patrick
reply other threads:[~2018-07-09 15:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAO=notwagKYN0XT4F3TU8EZntYUiQ0Z+wNzvhV9C6NnqSsDO2w@mail.gmail.com' \
--to=venture@google.com \
--cc=openbmc@lists.ozlabs.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).