From: Alexander Amelkin <a.amelkin@yadro.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: IPMI Adopter's agreement
Date: Wed, 20 Jun 2018 19:32:28 +0300 [thread overview]
Message-ID: <19fe4e16-c014-3af8-ac1f-a73b446b379e@yadro.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 234 bytes --]
Just wondering, does OpenBMC / TLF have this fine document signed?
https://www.intel.com/content/www/us/en/servers/ipmi/ipmi-home.html/#adopters
Or does each vendor need to sign this separately?
Sincerely,
Alexander.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2018-06-20 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 16:32 Alexander Amelkin [this message]
2018-06-26 18:49 ` IPMI Adopter's agreement James Mihm
2018-11-19 12:35 ` Alexander Amelkin
2018-11-20 17:42 ` James Mihm
2018-11-23 11:38 ` New IPMI spec (Was: IPMI Adopter's agreement) Alexander Amelkin
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=19fe4e16-c014-3af8-ac1f-a73b446b379e@yadro.com \
--to=a.amelkin@yadro.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).