All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 4/6] drm/i915/bios: Fix aggressiveness typos
Date: Mon, 30 May 2022 15:33:06 +0300	[thread overview]
Message-ID: <87ilpnryil.fsf@intel.com> (raw)
In-Reply-To: <20220527204949.2264-5-ville.syrjala@linux.intel.com>

On Fri, 27 May 2022, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Fix various typos around "aggressiveness". Note that
> the VBT spec also sometimes missspells it as
> "agressiveness" so I guess that's where some of the typos
> came from.

Could nitpick unrelated things like space before ":" in bitfields or the
struct naming, but this patch does what it says on the box.

Reviewed-by: Jani Nikula <jani.nikula@intel.com>


>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_vbt_defs.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vbt_defs.h b/drivers/gpu/drm/i915/display/intel_vbt_defs.h
> index 4b98bab3b890..39109f204c6d 100644
> --- a/drivers/gpu/drm/i915/display/intel_vbt_defs.h
> +++ b/drivers/gpu/drm/i915/display/intel_vbt_defs.h
> @@ -856,9 +856,9 @@ struct als_data_entry {
>  	u16 lux;
>  } __packed;
>  
> -struct agressiveness_profile_entry {
> -	u8 dpst_agressiveness : 4;
> -	u8 lace_agressiveness : 4;
> +struct aggressiveness_profile_entry {
> +	u8 dpst_aggressiveness : 4;
> +	u8 lace_aggressiveness : 4;
>  } __packed;
>  
>  struct bdb_lfp_power {
> @@ -873,7 +873,7 @@ struct bdb_lfp_power {
>  	u16 dmrrs;
>  	u16 adb;
>  	u16 lace_enabled_status;
> -	struct agressiveness_profile_entry aggressivenes[16];
> +	struct aggressiveness_profile_entry aggressiveness[16];
>  	u16 hobl; /* 232+ */
>  	u16 vrr_feature_enabled; /* 233+ */
>  } __packed;

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-05-30 12:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 20:49 [Intel-gfx] [PATCH 0/6] drm/i915: Accept more fixed modes with VRR/DMRRS panels Ville Syrjala
2022-05-27 20:49 ` [Intel-gfx] [PATCH 1/6] drm/i915: Parse VRR capability from VBT Ville Syrjala
2022-05-30 12:18   ` Jani Nikula
2022-05-27 20:49 ` [Intel-gfx] [PATCH 2/6] drm/i915: Print out rejected fixed modes Ville Syrjala
2022-05-30 12:20   ` Jani Nikula
2022-05-27 20:49 ` [Intel-gfx] [PATCH 3/6] drm/i915: Accept more fixed modes with VRR panels Ville Syrjala
2022-05-30 12:31   ` Jani Nikula
2022-05-27 20:49 ` [Intel-gfx] [PATCH 4/6] drm/i915/bios: Fix aggressiveness typos Ville Syrjala
2022-05-30 12:33   ` Jani Nikula [this message]
2022-05-27 20:49 ` [Intel-gfx] [PATCH 5/6] drm/i915/bios: Define more BDB contents Ville Syrjala
2022-05-30 12:55   ` Jani Nikula
2022-05-31 18:24     ` Lyude Paul
2022-05-31 19:03     ` Ville Syrjälä
2022-05-27 20:49 ` [Intel-gfx] [PATCH 6/6] drm/i915: Treat DMRRS as static DRRS Ville Syrjala
2022-05-30 13:22   ` Jani Nikula
2022-05-30 13:26     ` Jani Nikula
2022-05-28 15:01 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Accept more fixed modes with VRR/DMRRS panels Patchwork

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=87ilpnryil.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.