#
99d292a3 |
| 08-Feb-2022 |
Willy Tu <wltu@google.com> |
phosphor-ipmi-flash: Code Health Cleanup
Removed the following warning. - using decl '*' is unused - 'push_back' is called inside a loop; consider pre-allocating the container capacity before th
phosphor-ipmi-flash: Code Health Cleanup
Removed the following warning. - using decl '*' is unused - 'push_back' is called inside a loop; consider pre-allocating the container capacity before the loop - function '*' defined in a header file; function definitions in header files can lead to ODR violations
Change-Id: I44e4b0f8056a853fb45b690394be1a8ebec45b20 Signed-off-by: Willy Tu <wltu@google.com>
show more ...
|
#
f450486f |
| 25-Apr-2021 |
Willy Tu <wltu@google.com> |
test: Replace the C++ MOCK_METHOD<n> macros with the new MOCK_METHOD Change-Id: I5099c727e9e918f19fa61acc91ef75250ebc6fa6 Signed-off-by: Willy Tu <wltu@google.com>
|
#
c78bfc82 |
| 05-Nov-2020 |
Jason Ling <jasonling@google.com> |
version-handler: add version-handler, blob handler Implement version-handler: a blob handler for retrieving version information about a blob. Problem: ipmi-flash(firmware-handle
version-handler: add version-handler, blob handler Implement version-handler: a blob handler for retrieving version information about a blob. Problem: ipmi-flash(firmware-handler) provides a mechanism to transfer firmware updates, verify them and perform updates but there is no mechanism to interrogate the firmware for its version. Solution: version-handler provides handlers for retrieving information about firmware blobs. Adding "version" syntax to "/flash/blob" entries in the json configuration file enables this feature. The mechanism to retrieve version is identical to the mechanism used by firmware-handler to perform preparation, verification and updates (kick off systemd targets). Signed-off-by: Jason Ling <jasonling@google.com> Change-Id: I28868ca8dd76d63af668d2e46b9359401d45f0bc
show more ...
|
#
84bff8be |
| 06-Nov-2020 |
Jason Ling <jasonling@google.com> |
test: move shared mocks to common area Move mocks that can be shared between version and firmware handler tests to parent directory (bmc/test). This will eliminate the need to d
test: move shared mocks to common area Move mocks that can be shared between version and firmware handler tests to parent directory (bmc/test). This will eliminate the need to duplicate the definition of testing mocks. Signed-off-by: Jason Ling <jasonling@google.com> Change-Id: Id41c56271d0bfbcb8c18da1f903c7786699508d4
show more ...
|
Revision tags: v1.0 |
|
#
f0c71df2 |
| 26-Jun-2019 |
Patrick Venture <venture@google.com> |
move bmc code into bmc folder Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I2407359461a1a2f0e733ff8cd0cb1744b6304c32
|