From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] tools: rename intel_bios_reader to intel_vbt_decode
Date: Tue, 24 Jan 2017 16:42:07 +0200 [thread overview]
Message-ID: <87y3y05xkw.fsf@intel.com> (raw)
In-Reply-To: <1485268660-3319-2-git-send-email-jani.nikula@intel.com>
On Tue, 24 Jan 2017, Jani Nikula <jani.nikula@intel.com> wrote:
> 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.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> ---
>
> Patch 6/6 with -M option.
*sigh*, fumbles with git send-email. All the three copies of 6/6 should
have identical effect, but just one of them was sent with rename
detection.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-24 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 14:30 [igt PATCH 1/6] intel_bios_reader: add more structured printout of headers Jani Nikula
2017-01-24 14:30 ` [igt PATCH 2/6] intel_bios_reader: abstract a more generic hex dumper Jani Nikula
2017-01-24 14:30 ` [igt PATCH 3/6] intel_bios_reader: add hex dumping of headers Jani Nikula
2017-01-24 14:30 ` [igt PATCH 4/6] intel_bios_reader: be more informative about unknown blocks Jani Nikula
2017-01-24 14:30 ` [igt PATCH 5/6] intel_bios_reader: print more VBT and BDB header info Jani Nikula
2017-01-24 14:30 ` [igt PATCH 6/6] tools: rename intel_bios_reader to intel_vbt_decode Jani Nikula
2017-01-24 14:37 ` [PATCH] " Jani Nikula
2017-01-24 14:37 ` [PATCH v2] " Jani Nikula
2017-01-24 14:42 ` Jani Nikula [this message]
2017-01-30 8:00 ` [PATCH] " Jani Nikula
2017-01-30 13:20 ` Ville Syrjälä
2017-01-31 14:38 ` Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3y05xkw.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).