libfdt: Fix a few typos

Fix 'saftey' and 'additional' typos noticed in the assumption series.
Reword the ASSUME_NO_ROLLBACK slightly to improve clarity.

Signed-off-by: Simon Glass <sjg@chromium.org>
Suggested-by: David Gibson <david@gibson.dropbear.id.au>
Message-Id: <20200302190255.51426-1-sjg@chromium.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
main
Simon Glass 2020-03-02 12:02:52 -07:00 committed by David Gibson
parent 0f61c72ded
commit fc207c3234
1 changed files with 3 additions and 3 deletions

View File

@ -58,7 +58,7 @@ static inline struct fdt_reserve_entry *fdt_mem_rsv_w_(void *fdt, int n)


/* /*
* Defines assumptions which can be enabled. Each of these can be enabled * Defines assumptions which can be enabled. Each of these can be enabled
* individually. For maximum saftey, don't enable any assumptions! * individually. For maximum safety, don't enable any assumptions!
* *
* For minimal code size and no safety, use ASSUME_PERFECT at your own risk. * For minimal code size and no safety, use ASSUME_PERFECT at your own risk.
* You should have another method of validating the device tree, such as a * You should have another method of validating the device tree, such as a
@ -121,8 +121,8 @@ enum {
ASSUME_LATEST = 1 << 2, ASSUME_LATEST = 1 << 2,


/* /*
* This assume that it is OK for a failed additional to the device tree * This assumes that it is OK for a failed addition to the device tree,
* due to lack of space or some other problem can skip any rollback * due to lack of space or some other problem, to skip any rollback
* steps (such as dropping the property name from the string table). * steps (such as dropping the property name from the string table).
* This is safe to enable in most circumstances, even though it may * This is safe to enable in most circumstances, even though it may
* leave the tree in a sub-optimal state. * leave the tree in a sub-optimal state.