Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nemesa Garg <nemesa.garg@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Nemesa Garg <nemesa.garg@intel.com>
Subject: Re: [PATCH 1/3] drm/i915/display: Modify panel_fitting code for joiner
Date: Wed, 25 Sep 2024 12:11:43 +0300	[thread overview]
Message-ID: <87seto2j3k.fsf@intel.com> (raw)
In-Reply-To: <20240925063032.2311796-2-nemesa.garg@intel.com>

On Wed, 25 Sep 2024, Nemesa Garg <nemesa.garg@intel.com> wrote:
> @@ -666,16 +666,16 @@ static int gmch_panel_fitting(struct intel_crtc_state *crtc_state,
>  	return 0;
>  }
>  
> -int intel_panel_fitting(struct intel_crtc_state *crtc_state,
> -			const struct drm_connector_state *conn_state)
> +int intel_gch_panel_fitting(struct intel_crtc_state *crtc_state,
> +			    const struct drm_connector_state *conn_state)

What's gch supposed to mean?


-- 
Jani Nikula, Intel

  reply	other threads:[~2024-09-25  9:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25  6:30 [PATCH 0/3] Consider joiner calculation for panel fitting Nemesa Garg
2024-09-25  6:30 ` [PATCH 1/3] drm/i915/display: Modify panel_fitting code for joiner Nemesa Garg
2024-09-25  9:11   ` Jani Nikula [this message]
2024-09-25 12:30     ` Garg, Nemesa
2024-09-25 20:13   ` Ville Syrjälä
2024-09-25  6:30 ` [PATCH 2/3] drm/i915/display: Add gmch_panel_fitting in all encoders Nemesa Garg
2024-09-25  9:12   ` Jani Nikula
2024-09-25 12:28     ` Garg, Nemesa
2024-09-25 20:21   ` Ville Syrjälä
2024-09-25  6:30 ` [PATCH v4 3/3] drm/i915/display: Call panel_fitting from pipe_config Nemesa Garg
2024-09-25 19:22   ` kernel test robot
2024-09-25 20:36   ` Ville Syrjälä
2024-10-01  7:10   ` Dan Carpenter
2024-09-27  1:02 ` ✗ Fi.CI.SPARSE: warning for Consider joiner calculation for panel fitting (rev4) Patchwork
2024-09-27  1:11 ` ✗ Fi.CI.BAT: failure " 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=87seto2j3k.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nemesa.garg@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