#
8ca6dbcd |
| 04-Jan-2024 |
Krzysztof Karas <krzysztof.karas@intel.com> |
test/json_config: commonize functions
Commonize some of the functions to avoid code duplication.
Change-Id: I4ec1af2b803f9776e78f6f697dcba9739795d79b Signed-off-by: Krzysztof Karas <krzysztof.karas
test/json_config: commonize functions
Commonize some of the functions to avoid code duplication.
Change-Id: I4ec1af2b803f9776e78f6f697dcba9739795d79b Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/21259 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <jim.harris@samsung.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
show more ...
|
#
eb53c232 |
| 02-Nov-2022 |
paul luse <paul.e.luse@intel.com> |
add (c) and SPDX header to bash files as needed
per Intel policy to include file commit date using git cmd below. The policy does not apply to non-Intel (C) notices.
git log --follow -C90% --forma
add (c) and SPDX header to bash files as needed
per Intel policy to include file commit date using git cmd below. The policy does not apply to non-Intel (C) notices.
git log --follow -C90% --format=%ad --date default <file> | tail -1
and then pull just the year from the result.
Intel copyrights were not added to files where Intel either had no contribution ot the contribution lacked substance (ie license header updates, formatting changes, etc)
For intel copyrights added, --follow and -C95% were used.
Signed-off-by: paul luse <paul.e.luse@intel.com> Change-Id: I2ef86976095b88a9bf5b1003e59f3943cd6bbe4c Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15209 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
show more ...
|
#
921c92e2 |
| 12-Nov-2021 |
Tom Nabarro <tom.nabarro@intel.com> |
test/config: verify extra key in config doesnt break parsing
Add autotest case to verify that additional top-level key in JSON config file doesn't break parsing when loading and initializing subsyst
test/config: verify extra key in config doesnt break parsing
Add autotest case to verify that additional top-level key in JSON config file doesn't break parsing when loading and initializing subsystems from said file. This is a regression test to help applications use the same config file to communicate private and SPDK data.
Signed-off-by: Tom Nabarro <tom.nabarro@intel.com> Change-Id: I3ef6fe20d21398d30fa8011e20de1524e60ee841 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/10204 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Niu Yawei <yawei.niu@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
show more ...
|