#
42a44c28 |
| 16-Aug-2024 |
Patrick Williams <patrick@stwcx.xyz> |
clang-format: re-format for clang-18
clang-format-18 isn't compatible with the clang-format-17 output, so we need to reformat the code with the latest version. The way clang-18 handles lambda forma
clang-format: re-format for clang-18
clang-format-18 isn't compatible with the clang-format-17 output, so we need to reformat the code with the latest version. The way clang-18 handles lambda formatting also changed, so we have made changes to the organization default style format to better handle lambda formatting.
See I5e08687e696dd240402a2780158664b7113def0e for updated style. See Iea0776aaa7edd483fa395e23de25ebf5a6288f71 for clang-18 enablement.
Change-Id: I09e19a126d456dc184fd70e82d4e4e4217fa8ee7 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
show more ...
|
#
ded66d0f |
| 23-Oct-2020 |
Jason Ling <jasonling@google.com> |
move files around to create a common convenience library Problem: plan is to add another blob handler into ipmi-flash (ipmi-flash-version). This new handler will re-use much of the i
move files around to create a common convenience library Problem: plan is to add another blob handler into ipmi-flash (ipmi-flash-version). This new handler will re-use much of the ipmi-flash (firmware-handler) code. The common code should be presented as a convenience library to reduce code duplication. Solution: move anticipated firmware-handler specific code into the subdirectory bmc/firmware-handler and leave common code in bmc/. The end goal is to have version-handler re-use as much code as possible. Tested: rebuilt everything and ran unit tests. Signed-off-by: Jason Ling <jasonling@google.com> Change-Id: I2128da629b0ddf27b89f1faee358d1941f1dff38
show more ...
|