drivers/intel/fsp1_1: Fix issues detected by checkpatch
Fix the following error and warnings detected by checkpatch.pl:
ERROR: "foo * bar" should be "foo *bar"
WARNING: line over 80 characters
WARNING: else is not generally useful after a break or return
WARNING: braces {} are not necessary for single statement blocks
WARNING: suspect code indent for conditional statements (16, 32)
WARNING: Comparisons should place the constant on the right side of the test
TEST=Build and run on Galileo Gen2
Change-Id: I9f56c0b0e3baf84989411e4a4b98f935725c013f
Signed-off-by: Lee Leahy <Leroy.P.Leahy@intel.com>
Reviewed-on: https://review.coreboot.org/18886
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Philippe Mathieu-Daudé <philippe.mathieu.daude@gmail.com>
This commit is contained in:
@@ -183,7 +183,7 @@ void raminit(struct romstage_params *params)
|
||||
/* Locate the FSP_SMBIOS_MEMORY_INFO HOB */
|
||||
memory_info_hob = get_next_guid_hob(&memory_info_hob_guid,
|
||||
hob_list_ptr);
|
||||
if (NULL == memory_info_hob) {
|
||||
if (memory_info_hob == NULL) {
|
||||
printk(BIOS_ERR, "FSP_SMBIOS_MEMORY_INFO HOB missing!\n");
|
||||
fsp_verification_failure = 1;
|
||||
} else {
|
||||
@@ -205,7 +205,7 @@ void raminit(struct romstage_params *params)
|
||||
* 7.5: EFI_PEI_GRAPHICS_INFO_HOB produced by SiliconInit
|
||||
* FSP_SMBIOS_MEMORY_INFO HOB verified above
|
||||
*/
|
||||
if (NULL != cbmem_root) {
|
||||
if (cbmem_root != NULL) {
|
||||
printk(BIOS_DEBUG,
|
||||
"7.4: FSP_BOOTLOADER_TOLUM_HOB: 0x%p\n",
|
||||
cbmem_root);
|
||||
@@ -215,7 +215,7 @@ void raminit(struct romstage_params *params)
|
||||
printk(BIOS_DEBUG, " 0x%016lx: ResourceLength\n", data);
|
||||
}
|
||||
hob_ptr.Raw = get_next_guid_hob(&mrc_guid, hob_list_ptr);
|
||||
if (NULL == hob_ptr.Raw) {
|
||||
if (hob_ptr.Raw == NULL) {
|
||||
printk(BIOS_ERR, "7.3: FSP_NON_VOLATILE_STORAGE_HOB missing!\n");
|
||||
fsp_verification_failure =
|
||||
(params->pei_data->saved_data == NULL) ? 1 : 0;
|
||||
|
||||
Reference in New Issue
Block a user