payloads/libpayload: Add spaces around '=='
Change-Id: Ie1da925aceb01c2d21b472bf171000803004578f Signed-off-by: Elyes HAOUAS <ehaouas@noos.fr> Reviewed-on: https://review.coreboot.org/25856 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Julius Werner <jwerner@chromium.org>
This commit is contained in:
committed by
Patrick Georgi
parent
12f345d671
commit
00877386ee
@@ -52,7 +52,7 @@ MODULE_ID("$Id: m_attribs.c,v 1.16 2010/01/23 21:16:54 tom Exp $")
|
||||
NCURSES_IMPEXP int NCURSES_API set_menu_ ## name (MENU* menu, chtype attr) \
|
||||
{\
|
||||
T((T_CALLED("set_menu_" #name "(%p,%s)"), menu, _traceattr(attr))); \
|
||||
if (!(attr==A_NORMAL || (attr & A_ATTRIBUTES)==attr))\
|
||||
if (!(attr == A_NORMAL || (attr & A_ATTRIBUTES) == attr))\
|
||||
RETURN(E_BAD_ARGUMENT);\
|
||||
if (menu && ( menu -> name != attr))\
|
||||
{\
|
||||
|
@@ -180,7 +180,7 @@ _nc_Match_Next_Character_In_Item_Name
|
||||
or PREV_PATTERN scan this means, that there was no additional match.
|
||||
If we searched with an expanded new pattern, we should never reach
|
||||
this point, because if the expanded pattern matches also the actual
|
||||
item we will find it in the first attempt (passed==FALSE) and we
|
||||
item we will find it in the first attempt (passed == FALSE) and we
|
||||
will never cycle through the whole item array.
|
||||
*/
|
||||
assert(ch == 0 || ch == BS);
|
||||
|
Reference in New Issue
Block a user