From: "yugang.chen" <yugang.chen@linux.intel.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: "Bills, Jason M" <jason.m.bills@linux.intel.com>,
chunhui.jia@linux.intel.com
Subject: Re: apply for a new repo "openbmc/node-data-sync"
Date: Mon, 12 Apr 2021 14:38:38 +0800 [thread overview]
Message-ID: <bd64513a-76f6-7617-9942-ced892b2c500@linux.intel.com> (raw)
In-Reply-To: <AF9887DB-F6CB-4CE0-90B1-17FEA2497013@fuzziesquirrel.com>
thanks, Brad.
+ openbmc@lists.ozlabs.org .
Dear All,
I'm Intel BMC engineer, we have a module is used to sync sensor data between BMC nodes in one Chassis system. In our Modular system, there are 2 nodes or 4 nodes, one node works as Primary node, the other nodes work as secondary nodes.
1. Some sensors are only visible for primary BMC, but secondary nodes need the sensors for Fan control.
2. Some sensor are in secondary nodes, they are needed to show them on primary node.
So, we need a new repo to sync the sensor data between primary node and secondary nodes, could you create a repo "openbmc/node-data-sync"? thanks.
Best Regards
Daniel(Yugang)
On 4/10/2021 10:55 PM, Brad Bishop wrote:
> Hi Daniel
>
> Can you please send this to the mailing list so everyone can be aware of the work you are doing?
>
> thanks - brad
>
>> On Apr 7, 2021, at 1:31 AM, yugang.chen <yugang.chen@linux.intel.com> wrote:
>>
>> Hi Brad,
>>
>> I'm Intel BMC engineer, we have a module is used to sync sensor data between BMC nodes in one Chassis system. In our Modular system, there are 2 nodes or 4 nodes, one node works as Primary node, the other nodes work as secondary nodes.
>>
>> 1. Some sensors are only visible for primary BMC, but secondary nodes need the sensors for Fan control.
>>
>> 2. Some sensor are in secondary nodes, they are needed to show them on primary node.
>>
>> So, we need a new repo to sync the sensor data between primary node and secondary nodes, could you create a repo "openbmc/node-data-sync"? thanks.
>>
>>
>> Best Regards
>>
>> Daniel(Yugang)
>>
next parent reply other threads:[~2021-04-12 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cab2988f-76b8-6a30-5fa9-0ee8030af7f0@linux.intel.com>
[not found] ` <AF9887DB-F6CB-4CE0-90B1-17FEA2497013@fuzziesquirrel.com>
2021-04-12 6:38 ` yugang.chen [this message]
2021-04-12 11:29 ` apply for a new repo "openbmc/node-data-sync" Patrick Williams
2021-04-12 19:26 ` Ed Tanous
2021-04-19 4:41 ` yugang.chen
2021-04-19 14:26 ` Brad Bishop
2021-04-23 13:04 ` Patrick Williams
2021-04-19 5:10 Milton Miller II
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=bd64513a-76f6-7617-9942-ced892b2c500@linux.intel.com \
--to=yugang.chen@linux.intel.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=chunhui.jia@linux.intel.com \
--cc=jason.m.bills@linux.intel.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.