From: Imre Deak <imre.deak@intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <jani.nikula@linux.intel.com>
Subject: Re: [PATCH 1/2] drm/i915/dp: Make intel_dp_can_join() static
Date: Thu, 5 Feb 2026 11:44:47 +0200 [thread overview]
Message-ID: <aYRmj1ZF1renh3eP@ideak-desk.lan> (raw)
In-Reply-To: <20260205083623.793902-2-ankit.k.nautiyal@intel.com>
On Thu, Feb 05, 2026 at 02:06:22PM +0530, Ankit Nautiyal wrote:
> intel_dp_can_join() was previously exposed in intel_dp.h, but after the
> recent joiner refactor it is only used internally via
> intel_dp_joiner_candidate_valid(). It no longer needs external
> visibility, so make it static and drop the prototype from intel_dp.h.
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Reviewed-by: Imre Deak <imre.deak@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 1 +
> drivers/gpu/drm/i915/display/intel_dp.h | 2 --
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index e2fd01d1a1e4..4f5b89f80e55 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -1396,6 +1396,7 @@ bool intel_dp_has_dsc(const struct intel_connector *connector)
> return true;
> }
>
> +static
> bool intel_dp_can_join(struct intel_display *display,
> int num_joined_pipes)
> {
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.h b/drivers/gpu/drm/i915/display/intel_dp.h
> index ff527b351de0..cbd7fcd3789f 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.h
> +++ b/drivers/gpu/drm/i915/display/intel_dp.h
> @@ -222,8 +222,6 @@ int intel_dp_compute_config_late(struct intel_encoder *encoder,
> int intel_dp_sdp_min_guardband(const struct intel_crtc_state *crtc_state,
> bool assume_all_enabled);
> int intel_dp_max_hdisplay_per_pipe(struct intel_display *display);
> -bool intel_dp_can_join(struct intel_display *display,
> - int num_joined_pipes);
> bool intel_dp_dotclk_valid(struct intel_display *display,
> int target_clock,
> int htotal,
> --
> 2.45.2
>
next prev parent reply other threads:[~2026-02-05 9:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 8:36 [PATCH 0/2] drm/i915/dp: Joiner cleanups and fix Ankit Nautiyal
2026-02-05 8:36 ` [PATCH 1/2] drm/i915/dp: Make intel_dp_can_join() static Ankit Nautiyal
2026-02-05 9:44 ` Imre Deak [this message]
2026-02-05 8:36 ` [PATCH 2/2] drm/i915/dp: Restore the missing check for intel_dp_has_joiner Ankit Nautiyal
2026-02-05 9:41 ` Imre Deak
2026-02-05 12:37 ` Nautiyal, Ankit K
2026-02-05 12:53 ` Imre Deak
2026-02-05 14:20 ` Nautiyal, Ankit K
2026-02-06 4:47 ` Ankit Nautiyal
2026-02-06 10:33 ` Imre Deak
2026-02-05 12:30 ` ✓ i915.CI.BAT: success for drm/i915/dp: Joiner cleanups and fix Patchwork
2026-02-06 4:58 ` ✗ i915.CI.Full: failure " Patchwork
2026-02-06 6:06 ` ✓ i915.CI.BAT: success for drm/i915/dp: Joiner cleanups and fix (rev2) Patchwork
2026-02-07 4:20 ` ✗ i915.CI.Full: failure " Patchwork
2026-02-09 5:47 ` ✓ i915.CI.Full: success " 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=aYRmj1ZF1renh3eP@ideak-desk.lan \
--to=imre.deak@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox