openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Amelkin <a.amelkin@yadro.com>
To: James Mihm <james.mihm@gmail.com>
Cc: <openbmc@lists.ozlabs.org>
Subject: New IPMI spec (Was: IPMI Adopter's agreement)
Date: Fri, 23 Nov 2018 14:38:21 +0300	[thread overview]
Message-ID: <c6f86ba5-02ab-53e3-fa42-4b7d5fdbeed6@yadro.com> (raw)
In-Reply-To: <CADy_Pt0eQR5ZdRkjwc=5t4yB-YGbzfT9c=BFUrpgYnQ317rKZA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1088 bytes --]

James, do you by any chance know if there is any work in progress on a newer IPMI specification or is it a deprecated standard and will not be updated? I'm asking mostly because of https://github.com/openbmc/openbmc/issues/3417

Thank you.
Alexander.

20.11.2018 20:42, James Mihm wrote:
> I've refreshed my question internally, and expect to get a response next week.
> The person is out of the office until next week.
>
> James.On Mon, Nov 19, 2018 at 4:35 AM Alexander Amelkin
> <a.amelkin@yadro.com> wrote:
>> Any further info on this?
>>
>> 26.06.2018 21:49, James Mihm wrote:
>>> I'm looking into how we need to proceed regarding this question
>>> internally here at Intel.
>>>
>>> James.
>>> On Wed, Jun 20, 2018 at 9:33 AM Alexander Amelkin <a.amelkin@yadro.com> wrote:
>>>> 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 --]

      reply	other threads:[~2018-11-23 11:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 16:32 IPMI Adopter's agreement Alexander Amelkin
2018-06-26 18:49 ` James Mihm
2018-11-19 12:35   ` Alexander Amelkin
2018-11-20 17:42     ` James Mihm
2018-11-23 11:38       ` Alexander Amelkin [this message]

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=c6f86ba5-02ab-53e3-fa42-4b7d5fdbeed6@yadro.com \
    --to=a.amelkin@yadro.com \
    --cc=james.mihm@gmail.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).