diff options
| author | Jani Nikula <jani.nikula@intel.com> | 2017-01-24 16:24:59 +0200 |
|---|---|---|
| committer | Jani Nikula <jani.nikula@intel.com> | 2017-01-31 16:30:00 +0200 |
| commit | f609d1879355bae7747584a91b4b12e8dc502aef (patch) | |
| tree | 56e5c44a2f0347b8622ea8371fea7b8d6f9ef7ac /tools/intel_opregion_decode.c | |
| parent | 44023a2d8bddbbc6e89f05b69ab4f1a6a0079b7d (diff) | |
tools: rename intel_bios_reader to intel_vbt_decode
After all these years intel_bios_reader and intel_bios_dumper still
manage to confuse me. Read or dump, which one decodes. Rename
intel_bios_reader to intel_vbt_decode to be in line with the naming of
all the other tools (particularly the closely related
intel_opregion_decode tool) that decode previously gathered or dumped
information.
Acked-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'tools/intel_opregion_decode.c')
| -rw-r--r-- | tools/intel_opregion_decode.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/intel_opregion_decode.c b/tools/intel_opregion_decode.c index c65828ae..f532c1e2 100644 --- a/tools/intel_opregion_decode.c +++ b/tools/intel_opregion_decode.c @@ -327,7 +327,7 @@ static void decode_vbt(const void *buffer) printf("\tproduct string:\t%s\n", s); free(s); - printf("\t(use intel_bios_reader to decode the VBT)\n"); + printf("\t(use intel_vbt_decode to decode the VBT)\n"); printf("\n"); } |