summaryrefslogtreecommitdiff
path: root/BaseTools/Source/Python/CommonDataClass/CommonClass.py
diff options
context:
space:
mode:
authorRuiyu Ni <ruiyu.ni@intel.com>2016-11-11 12:12:51 +0800
committerRuiyu Ni <ruiyu.ni@intel.com>2016-11-16 12:32:17 +0800
commite9597b4519cbeda1c5175518f79a80d7f0b6353b (patch)
tree74851bbe884148457011dc7f2b59a45b8c5f7a83 /BaseTools/Source/Python/CommonDataClass/CommonClass.py
parent86a1eca2101686d476ab191f0511b44e369fd8a7 (diff)
downloadedk2-platforms-e9597b4519cbeda1c5175518f79a80d7f0b6353b.tar.xz
ShellPkg/dmpstore: Support "-sfo"
The patch adds the "-sfo" support to "dmpstore" command. When -l or -d is specified, -sfo is not supported. When the variable specified by name and GUID cannot be found, an error message is displayed; Otherwise, the SFO is displayed. E.g.: "dmpstore -guid GuidThatDoesntExist -sfo" produces output as: ShellCommand,"dmpstore" VariableInfo,"","GuidThatDoesntExist","","","" "dmpstore NameThatDoesntExist -guid GuidThatDoesntExist -sfo" produces output as: ShellCommand,"dmpstore" dmpstore: No matching variables found. Guid GuidThatDoesntExist, Name NameThatDoesntExist The difference between the above 2 cases is that former one only specifies the GUID, but the latter one specifies both name and GUID. Since not specifying GUID means to use GlobalVariableGuid, "dmpstore NameThatDoesntExist -sfo" produces the similar output as latter one. I personally prefer to always produce SFO output for both cases. But the above behavior is the discussion result between HPE engineers. Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com> Signed-off-by: Chen A Chen <chen.a.chen@intel.com> Reviewed-by: Jaben Carsey <jaben.carsey@intel.com> Reviewed-by: Tapan Shah <tapandshah@hpe.com>
Diffstat (limited to 'BaseTools/Source/Python/CommonDataClass/CommonClass.py')
0 files changed, 0 insertions, 0 deletions