All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t] lib/igt_kms: Don't read max dotclock on non-display platforms
Date: Wed, 15 Nov 2023 13:07:28 +0200	[thread overview]
Message-ID: <ZVSmcDIr7pVS_odg@intel.com> (raw)
In-Reply-To: <20231115090605.1506704-1-bhanuprakash.modem@intel.com>

On Wed, Nov 15, 2023 at 02:36:05PM +0530, Bhanuprakash Modem wrote:
> On non-display platforms, there is no point in checking for
> max dotclock.
> 
> Fixes: https://gitlab.freedesktop.org/drm/intel/-/issues/9672
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> ---
>  lib/igt_kms.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/igt_kms.c b/lib/igt_kms.c
> index 89510ff22..2073fae53 100644
> --- a/lib/igt_kms.c
> +++ b/lib/igt_kms.c
> @@ -6056,7 +6056,8 @@ int igt_get_max_dotclock(int fd)
>  	char *s;
>  	int dir, res, max_dotclock = 0;
>  
> -	if (!is_intel_device(fd))
> +	/* If there is no display, then no point to check for dotclock. */
> +	if (!is_intel_device(fd) || !drmModeGetResources(fd))

That will leak.

>  		return max_dotclock;
>  
>  	dir = igt_debugfs_dir(fd);
> -- 
> 2.40.0

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2023-11-15 11:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15  9:06 [igt-dev] [i-g-t] lib/igt_kms: Don't read max dotclock on non-display platforms Bhanuprakash Modem
2023-11-15  9:59 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-11-15 10:19 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-11-15 11:07 ` Ville Syrjälä [this message]
2023-11-15 12:01   ` [igt-dev] [i-g-t] " Modem, Bhanuprakash
2023-11-17  0:58 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=ZVSmcDIr7pVS_odg@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=bhanuprakash.modem@intel.com \
    --cc=igt-dev@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 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.