* [Patch] BaseTools: Fix the Keyword error for <ExtendedFvEntry> in FDF File
@ 2017-10-09 13:36 Yonghong Zhu
2017-10-11 4:47 ` Gao, Liming
0 siblings, 1 reply; 2+ messages in thread
From: Yonghong Zhu @ 2017-10-09 13:36 UTC (permalink / raw)
To: edk2-devel; +Cc: Liming Gao
current in FDF spec 3.6 [FV] section it use "FV_EXT_ENTRY_TYPE" as
Keyword for <ExtendedFvEntry>, while in the code it use "FV_EXT_ENTRY".
To keep compatibility, this patch support both keyword in the code
first.
Cc: Liming Gao <liming.gao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
---
BaseTools/Source/Python/GenFds/FdfParser.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/BaseTools/Source/Python/GenFds/FdfParser.py b/BaseTools/Source/Python/GenFds/FdfParser.py
index b95afc7..0190be8 100644
--- a/BaseTools/Source/Python/GenFds/FdfParser.py
+++ b/BaseTools/Source/Python/GenFds/FdfParser.py
@@ -2363,11 +2363,11 @@ class FdfParser:
return True
def __GetFvExtEntryStatement(self, FvObj):
- if not self.__IsKeyword( "FV_EXT_ENTRY"):
+ if not (self.__IsKeyword( "FV_EXT_ENTRY") or self.__IsKeyword( "FV_EXT_ENTRY_TYPE")):
return False
if not self.__IsKeyword ("TYPE"):
raise Warning("expected 'TYPE'", self.FileName, self.CurrentLineNumber)
--
2.6.1.windows.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [Patch] BaseTools: Fix the Keyword error for <ExtendedFvEntry> in FDF File
2017-10-09 13:36 [Patch] BaseTools: Fix the Keyword error for <ExtendedFvEntry> in FDF File Yonghong Zhu
@ 2017-10-11 4:47 ` Gao, Liming
0 siblings, 0 replies; 2+ messages in thread
From: Gao, Liming @ 2017-10-11 4:47 UTC (permalink / raw)
To: Zhu, Yonghong, edk2-devel@lists.01.org
Reviewed-by: Liming Gao <liming.gao@intel.com>
>-----Original Message-----
>From: Zhu, Yonghong
>Sent: Monday, October 09, 2017 9:37 PM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming <liming.gao@intel.com>
>Subject: [Patch] BaseTools: Fix the Keyword error for <ExtendedFvEntry> in
>FDF File
>
>current in FDF spec 3.6 [FV] section it use "FV_EXT_ENTRY_TYPE" as
>Keyword for <ExtendedFvEntry>, while in the code it use "FV_EXT_ENTRY".
>To keep compatibility, this patch support both keyword in the code
>first.
>
>Cc: Liming Gao <liming.gao@intel.com>
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
>---
> BaseTools/Source/Python/GenFds/FdfParser.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/BaseTools/Source/Python/GenFds/FdfParser.py
>b/BaseTools/Source/Python/GenFds/FdfParser.py
>index b95afc7..0190be8 100644
>--- a/BaseTools/Source/Python/GenFds/FdfParser.py
>+++ b/BaseTools/Source/Python/GenFds/FdfParser.py
>@@ -2363,11 +2363,11 @@ class FdfParser:
>
> return True
>
> def __GetFvExtEntryStatement(self, FvObj):
>
>- if not self.__IsKeyword( "FV_EXT_ENTRY"):
>+ if not (self.__IsKeyword( "FV_EXT_ENTRY") or
>self.__IsKeyword( "FV_EXT_ENTRY_TYPE")):
> return False
>
> if not self.__IsKeyword ("TYPE"):
> raise Warning("expected 'TYPE'", self.FileName,
>self.CurrentLineNumber)
>
>--
>2.6.1.windows.1
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-10-11 4:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-10-09 13:36 [Patch] BaseTools: Fix the Keyword error for <ExtendedFvEntry> in FDF File Yonghong Zhu
2017-10-11 4:47 ` Gao, Liming
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox