From: James Feist <james.feist@linux.intel.com>
To: Gunnar Mills <gmills@linux.vnet.ibm.com>,
Joseph Reynolds <jrey@linux.ibm.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: jason.m.bills@linux.intel.com, apparao.puli@linux.intel.com
Subject: Re: Redfish OpenBMC OEM
Date: Wed, 29 Jan 2020 09:20:59 -0800 [thread overview]
Message-ID: <bdedea87-1400-7aa3-e1dc-a1c915b2cdb0@linux.intel.com> (raw)
In-Reply-To: <2b781d56-e375-96a9-c83d-87e07f0d00dd@linux.vnet.ibm.com>
> Did we engage Redfish on this one
> https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/28699 ?
Yes, from the comments:
"Was this brought up to DMTF?
https://github.com/openbmc/bmcweb/commit/40d68ef6ebe088e4cd0078f8ff4910ca58f2be5d
I've created new thread on Redfish forum:
https://redfishforum.com/thread/273/extending-virtualmedia-schema-proposal"
>
> Should the schema go in a different repo, and have a different review
> process? Maybe a minimum of N contributing companies have to sign off on
> the interface definition of a Redfish "OpenBMC" OEM? Do others have a
> similar concern?
>
> Thanks!
> Gunnar
>
next prev parent reply other threads:[~2020-01-29 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 16:23 Redfish OpenBMC OEM Gunnar Mills
2019-11-19 18:03 ` Joseph Reynolds
2019-11-19 19:04 ` James Feist
2019-11-20 15:57 ` Joseph Reynolds
2019-11-20 17:47 ` James Feist
2019-11-20 22:45 ` Gunnar Mills
2019-11-20 23:50 ` James Feist
2019-11-21 15:39 ` Gunnar Mills
2019-11-21 18:16 ` James Feist
2019-11-21 19:22 ` Gunnar Mills
2019-11-22 17:17 ` Redfish OpenBMC OEM - password not accepted Joseph Reynolds
2020-01-29 16:47 ` Redfish OpenBMC OEM Gunnar Mills
2020-01-29 17:20 ` James Feist [this message]
2020-01-29 19:42 ` Gunnar Mills
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=bdedea87-1400-7aa3-e1dc-a1c915b2cdb0@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=apparao.puli@linux.intel.com \
--cc=gmills@linux.vnet.ibm.com \
--cc=jason.m.bills@linux.intel.com \
--cc=jrey@linux.ibm.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 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.