From: Jani Nikula <jani.nikula@linux.intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: "Alan Previn" <alan.previn.teres.alexis@intel.com>,
"José Roberto de Souza" <jose.souza@intel.com>
Subject: Re: [PATCH] drm/i915: Do not print 'pxp init failed with 0' when it succeed
Date: Thu, 21 Mar 2024 14:38:18 +0200 [thread overview]
Message-ID: <87bk77n4jp.fsf@intel.com> (raw)
In-Reply-To: <20240320210547.71937-1-jose.souza@intel.com>
On Wed, 20 Mar 2024, José Roberto de Souza <jose.souza@intel.com> wrote:
> It is misleading, if the intention was to also print something
> in case it succeed it should have a different string.
>
> Cc: Alan Previn <alan.previn.teres.alexis@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
Fixes: 698e19da2914 ("drm/i915: Skip pxp init if gt is wedged")
Cc: <stable@vger.kernel.org> # v6.8+
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/i915_driver.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> index 9ee902d5b72c4..4b9233c07a22c 100644
> --- a/drivers/gpu/drm/i915/i915_driver.c
> +++ b/drivers/gpu/drm/i915/i915_driver.c
> @@ -800,7 +800,7 @@ int i915_driver_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> goto out_cleanup_modeset2;
>
> ret = intel_pxp_init(i915);
> - if (ret != -ENODEV)
> + if (ret && ret != -ENODEV)
> drm_dbg(&i915->drm, "pxp init failed with %d\n", ret);
>
> ret = intel_display_driver_probe(i915);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-03-21 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 21:05 [PATCH] drm/i915: Do not print 'pxp init failed with 0' when it succeed José Roberto de Souza
2024-03-21 2:29 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-03-21 12:38 ` Jani Nikula [this message]
2024-03-21 14:27 ` [PATCH] " Souza, Jose
2024-03-22 1:00 ` ✗ 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=87bk77n4jp.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@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.