From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 03/13] tools/intel_vbt_decode: Allow blocks to be named without full decoding
Date: Thu, 11 Apr 2024 16:15:24 +0300 [thread overview]
Message-ID: <ZhfibKZyDCe7jJn6@intel.com> (raw)
In-Reply-To: <87frvs59gw.fsf@intel.com>
On Thu, Apr 11, 2024 at 04:12:47PM +0300, Jani Nikula wrote:
> On Thu, 11 Apr 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> > On Fri, 22 Mar 2024, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> >> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>
> >> Make it possible to give blocks a name without having to
> >> implement full decoding.
> >>
> >> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Good idea!
> >
> > Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> I was expecting to see a patch adding all those block names without
> decoding. In the follow-up, then?
Yeah, there be more coming.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-04-11 13:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 20:41 [PATCH i-g-t 00/13] tools/intel_vbt_decode: Various improvement Ville Syrjala
2024-03-22 20:41 ` [PATCH i-g-t 01/13] tools/intel_vbt_decode: update vbt defs from kernel Ville Syrjala
2024-04-11 12:20 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 02/13] tools/intel_vbt_decode: Extract default_algorithm() Ville Syrjala
2024-04-11 12:20 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 03/13] tools/intel_vbt_decode: Allow blocks to be named without full decoding Ville Syrjala
2024-04-11 12:22 ` Jani Nikula
2024-04-11 13:12 ` Jani Nikula
2024-04-11 13:15 ` Ville Syrjälä [this message]
2024-03-22 20:41 ` [PATCH i-g-t 04/13] tools/intel_vbt_decode: Print the block min size Ville Syrjala
2024-04-11 12:24 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 05/13] tools/intel_vbt_decode: Dump AIM offsets Ville Syrjala
2024-04-11 12:25 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 06/13] tools/intel_vbt_decode: Decode the backlight i2c stuff Ville Syrjala
2024-04-11 12:44 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 07/13] tools/intel_vbt_decode: Decode the obsolote DPST supported field Ville Syrjala
2024-04-11 12:46 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 08/13] tools/intel_vbt_decode: Check version before decoding lace_aggressiveness_profile Ville Syrjala
2024-04-11 13:03 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 09/13] tools/intel_vbt_decode: Add version checks for backlight decoding Ville Syrjala
2024-04-11 13:06 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 10/13] tools/intel_vbt_decode: Dump out the backlight entry size Ville Syrjala
2024-04-11 13:06 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 11/13] tools/intel_vbt_decode: Dump MIPI sequences in the order they appear in VBT Ville Syrjala
2024-04-11 13:08 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 12/13] tools/intel_vbt_decode: Decode all the driver feature bits Ville Syrjala
2024-04-11 13:10 ` Jani Nikula
2024-03-22 20:41 ` [PATCH i-g-t 13/13] tools/intel_vbt_decode: Decode the EFP index Ville Syrjala
2024-04-11 13:11 ` Jani Nikula
2024-03-22 23:39 ` ✓ CI.xeBAT: success for tools/intel_vbt_decode: Various improvement Patchwork
2024-03-22 23:56 ` ✓ Fi.CI.BAT: " Patchwork
2024-03-23 22:43 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-13 13:13 ` [PATCH i-g-t 00/13] " Kamil Konieczny
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=ZhfibKZyDCe7jJn6@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
/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