ARMmbed
/
mbed-os
mirror of https://github.com/ARMmbed/mbed-os.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix typos in comments

pull/11358/head
Kyle Kearney 2019-08-23 10:58:57 -07:00 committed by Martin Kojtal
parent 4a0ca21edd
commit 5820a3172f
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
features/storage/kvstore/conf/kv_config.cpp
View File

@ -388,7 +388,7 @@ BlockDevice *_get_blockdevice_FLASHIAP(bd_addr_t start_address, bd_size_t size)
}
if (size == 0) {
//The block device will have all space form start address to the end of the flash
//The block device will have all space from start address to the end of the flash
size = (flash_end_address - start_address);
static FlashIAPBlockDevice bd(start_address, size);

4
features/storage/kvstore/tdbstore/TDBStore.cpp
View File

@ -614,7 +614,7 @@ int TDBStore::set_finalize(set_handle_t handle)
goto end;
}
// Writes may fail without returning a failure (specially in flash components). Reread the record
// Writes may fail without returning a failure (especially in flash components). Reread the record
// to ensure write success (this won't read the data anywhere - just use the CRC calculation).
ret = read_record(_active_area, ih->bd_base_offset, 0, 0, (uint32_t) -1,
actual_data_size, 0, false, false, false, false,
@ -1061,7 +1061,7 @@ int TDBStore::init()
// (this will do nothing if already erased)
if (ret == MBED_ERROR_INVALID_DATA_DETECTED) {
if (check_erase_before_write(area, _master_record_offset, _master_record_size, true)) {
MBED_ERROR(MBED_ERROR_READ_FAILED, "TDBSTORE: Unable reset area at init");
MBED_ERROR(MBED_ERROR_READ_FAILED, "TDBSTORE: Unable to reset area at init");
}
area_state[area] = TDBSTORE_AREA_STATE_EMPTY;
continue;

4
platform/source/mbed_error.c
View File

@ -139,8 +139,8 @@ static mbed_error_status_t handle_error(mbed_error_status_t error_status, unsign
//Error status should always be < 0
if (error_status >= 0) {
//This is a weird situation, someone called mbed_error with invalid error code.
//We will still handle the situation but change the error code to ERROR_INVALID_ARGUMENT, atleast the context will have info on who called it
//This is a weird situation, someone called mbed_error with an invalid error code.
//We will still handle the situation but change the error code to ERROR_INVALID_ARGUMENT, at least the context will have info on who called it
error_status = MBED_ERROR_INVALID_ARGUMENT;
}