| commit | 440f62bfd5eb557059e76b1d5d7a107ce67ba8ed | [log] [tgz] |
|---|---|---|
| author | Manish Baing <manish.baing@intel.com> | Thu Jul 15 22:00:37 2021 +0000 |
| committer | manish.baing <manish.baing@intel.com> | Fri Jul 16 14:22:03 2021 +0000 |
| tree | 716898a5d98dc4388ec5580999e6427da186b590 | |
| parent | 9f8d027a411c77b13a92d3eae2fcc9747f484a3c [diff] |
Reset ChannelInfo before calling getChannelInfo()
chInfo is initialized with '0' in statement 'ChannelInfo chInfo{};'
This is to make sure even if getChannelInfo function fails to update
chInfo,un-initialized/previous chInfo data will not be used for
further execution in function ipmiOEMSetUser2Activation.
Tested:
By printing structure chInfo for each IPMI channel
before calling getChannelInfo function, we observed that
'chInfo' structure intialized with zeroes for each IPMI channel.
Signed-off-by: Manish Baing <manish.baing@intel.com>
Change-Id: I0fcfabd30d05f4d360758cff31bb98fff01c5f7e
This component is intended to provide Intel-specific IPMI[3] command handlers for OpenBMC. These handlers are intended to integrate BMC with servers based on Intel architecture.
intel-ipmi-oem serves as an extension[1] to OpenBMC IPMI daemon[2]. It is compiled as a shared library and intended to both:
Related features provided by the library are grouped in separate source files. Main extensions to vanilla OpenBMC IPMI stack are the following:
[4]