From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: "Wang, Kuiying" <kuiying.wang@intel.com>
Cc: "geissonator@yahoo.com" <geissonator@yahoo.com>,
"tomjoseph@in.ibm.com" <tomjoseph@in.ibm.com>,
"Tanous, Ed" <ed.tanous@intel.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"yong.b.li@linux.intel.com" <yong.b.li@linux.intel.com>,
"Li, Yong B" <yong.b.li@intel.com>,
"openbmc-ci-admin@ozlabs.org" <openbmc-ci-admin@ozlabs.org>,
"richard.marian.thomaiyar@linux.intel.com"
<richard.marian.thomaiyar@linux.intel.com>,
"Mihm, James" <james.mihm@intel.com>
Subject: Re: Need create a repo for chassis implementation.
Date: Tue, 7 Aug 2018 08:34:09 -0400 [thread overview]
Message-ID: <84A1C7CA-5072-4D0A-BC25-9EB8717E5AC5@fuzziesquirrel.com> (raw)
In-Reply-To: <959CAFA1E282D14FB901BE9A7BF4E77249DE8512@SHSMSX101.ccr.corp.intel.com>
> On Aug 6, 2018, at 9:41 PM, Wang, Kuiying <kuiying.wang@intel.com> wrote:
>
> Hi Brad,
> Thanks a lot for your support.
> 1. I have already written this program on OpenBMC and verified it on X86 platform WFP.
> 2. No need for specify Dbus API for x86-power-control, all the APIs are common.
>
> BTW:
> Can you add me or other Intel member into the maintainer list for these two repos?
Please add a MAINTAINERS file in one of your patches and I’ll
add those individuals to the necessary groups.
>
>
> Thanks,
> Kuiying.
next prev parent reply other threads:[~2018-08-07 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 2:46 Need create a repo for chassis implementation Wang, Kuiying
2018-07-25 10:14 ` Brad Bishop
2018-07-26 2:33 ` Wang, Kuiying
2018-08-03 20:08 ` Brad Bishop
2018-08-07 1:41 ` Wang, Kuiying
2018-08-07 12:34 ` Brad Bishop [this message]
2018-08-08 1:46 ` Wang, Kuiying
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=84A1C7CA-5072-4D0A-BC25-9EB8717E5AC5@fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=ed.tanous@intel.com \
--cc=geissonator@yahoo.com \
--cc=james.mihm@intel.com \
--cc=kuiying.wang@intel.com \
--cc=openbmc-ci-admin@ozlabs.org \
--cc=openbmc@lists.ozlabs.org \
--cc=richard.marian.thomaiyar@linux.intel.com \
--cc=tomjoseph@in.ibm.com \
--cc=yong.b.li@intel.com \
--cc=yong.b.li@linux.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 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).