chore: cosmetic manifest parsing error printing
Omit full stop for error messages in manifest_strerror.
Remove printing the error message from parse_ffa_partition_package as
this is redundant with the message printed by [1].
[1] https://git.trustedfirmware.org/hafnium/hafnium.git/tree/src/init.c?h=v2.9#n145
Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
Change-Id: I1b54cb726a682e7a2b6b8f94f98b7ee41c0be76f
diff --git a/src/manifest.c b/src/manifest.c
index 54d480e..46d635e 100644
--- a/src/manifest.c
+++ b/src/manifest.c
@@ -1263,8 +1263,7 @@
ret = parse_ffa_manifest(&sp_fdt, vm, &boot_info_node, boot_params);
if (ret != MANIFEST_SUCCESS) {
- dlog_error("Error parsing partition manifest: %s.\n",
- manifest_strerror(ret));
+ dlog_error("Error parsing partition manifest.\n");
goto out;
}
@@ -1487,14 +1486,13 @@
"response to Other-S Interrupt";
case MANIFEST_ERROR_MEMORY_MISSING:
return "Memory nodes must be defined in the SPMC manifest "
- "('memory' and 'ns-memory').";
+ "('memory' and 'ns-memory')";
case MANIFEST_ERROR_PARTITION_ADDRESS_OVERLAP:
return "Partition's memory [load address: load address + "
"memory size[ overlap with other allocated "
- "regions.";
+ "regions";
case MANIFEST_ERROR_MEM_REGION_INVALID:
- return "Memory region must within memory ranges defined "
- "in the SPMC manifest.";
+ return "Invalid memory region range";
case MANIFEST_ERROR_INVALID_BOOT_ORDER:
return "Boot order should be a unique value less than "
"default largest value";