summaryrefslogtreecommitdiffstats
path: root/BaseTools/Source/Python/AutoGen/IdfClassObject.py
diff options
context:
space:
mode:
authorDandan Bi <dandan.bi@intel.com>2018-10-11 14:37:09 +0800
committerHao Wu <hao.a.wu@intel.com>2018-10-26 15:08:40 +0800
commitadb2c050128c62ab96bdec95f648f9a18603b028 (patch)
tree05cd7f551339d71abdc8064960b168ee3472214c /BaseTools/Source/Python/AutoGen/IdfClassObject.py
parent599bb2be1f2b119dcde9e5a7515dc6f3d19eb29d (diff)
downloadedk2-adb2c050128c62ab96bdec95f648f9a18603b028.tar.gz
edk2-adb2c050128c62ab96bdec95f648f9a18603b028.tar.bz2
edk2-adb2c050128c62ab96bdec95f648f9a18603b028.zip
MdeModulePkg/HiiDB: Reorganize codes of exporting HII settings
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1235 Function "HiiGetConfigurationSetting" may be called when HiiDatabase contents have been updated. And it is just to call function "HiiGetDatabaseInfo" to get the contents in HiiDatabase and call function "HiiGetConfigRespInfo" and get the configuration response string form HII drivers. So here we can remove function "HiiGetConfigurationSetting" and make caller to call "HiiGetDatabaseInfo" and "HiiGetConfigRespInfo" directly. And thus it also can distinguish which code blocks are to operate HiiDatabase contents and which code blocks are not. Then it's easy to know which code blocks should be atomic when updating HiiDatabase contents. Cc: Liming Gao <liming.gao@intel.com> Cc: Eric Dong <eric.dong@intel.com> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Dandan Bi <dandan.bi@intel.com> Reviewed-by: Liming Gao <liming.gao@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/AutoGen/IdfClassObject.py')
0 files changed, 0 insertions, 0 deletions