From 124ef38f7afc61ad7c713c22aad7c5c7f79bdb9b Mon Sep 17 00:00:00 2001 From: Elyes HAOUAS Date: Tue, 27 Mar 2018 12:15:09 +0200 Subject: Fix whitespace errors Change-Id: Ic2d3bb9d8581a0471a8568a130f893b34dddf113 Signed-off-by: Elyes HAOUAS Reviewed-on: https://review.coreboot.org/25380 Tested-by: build bot (Jenkins) Reviewed-by: Nico Huber --- coreboot_tables.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'coreboot_tables.h') diff --git a/coreboot_tables.h b/coreboot_tables.h index 2e9652670..a5f1586fd 100644 --- a/coreboot_tables.h +++ b/coreboot_tables.h @@ -29,7 +29,7 @@ * is expected to be information that cannot be discovered by * other means, such as querying the hardware directly. * - * All of the information should be Position Independent Data. + * All of the information should be Position Independent Data. * That is it should be safe to relocated any of the information * without it's meaning/correctness changing. For table that * can reasonably be used on multiple architectures the data @@ -52,9 +52,9 @@ * table entries and be backwards compatible, but it is not required. */ -/* Since coreboot is usually compiled 32bit, gcc will align 64bit - * types to 32bit boundaries. If the coreboot table is dumped on a - * 64bit system, a uint64_t would be aligned to 64bit boundaries, +/* Since coreboot is usually compiled 32bit, gcc will align 64bit + * types to 32bit boundaries. If the coreboot table is dumped on a + * 64bit system, a uint64_t would be aligned to 64bit boundaries, * breaking the table format. * * lb_uint64 will keep 64bit coreboot table values aligned to 32bit -- cgit v1.2.3