From: Andi Shyti <andi.shyti@linux.intel.com>
To: John.C.Harrison@intel.com
Cc: Alan Previn <alan.previn.teres.alexis@intel.com>,
Jani Nikula <jani.nikula@intel.com>,
Intel-GFX@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>,
DRI-Devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i1915/guc: Fix probe injection CI failures after recent change
Date: Fri, 12 May 2023 12:17:24 +0200 [thread overview]
Message-ID: <ZF4SNE/XNXi75W5d@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230510205556.312999-1-John.C.Harrison@Intel.com>
Hi John,
On Wed, May 10, 2023 at 01:55:56PM -0700, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> A recent change bumped a 'notice' message up to 'error' level for
> debug builds to help trap incorrect configurations in CI systems.
> Unfortunaetly, tha error condition in question is triggered by the
/tha/the/
> error injection probe test. So change the message again to be 'probe
> error' level instead.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> Fixes: 760133d42f0a ("drm/i915/uc: Make unexpected firmware versions an error in debug builds")
> Cc: John Harrison <John.C.Harrison@Intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Alan Previn <alan.previn.teres.alexis@intel.com>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Andi
> ---
> drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> index 4ec7df9ed5ff3..e467d9af61876 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> @@ -18,7 +18,7 @@
> #include "i915_reg.h"
>
> #if IS_ENABLED(CONFIG_DRM_I915_DEBUG_GEM)
> -#define UNEXPECTED gt_err
> +#define UNEXPECTED gt_probe_error
> #else
> #define UNEXPECTED gt_notice
> #endif
> --
> 2.39.1
prev parent reply other threads:[~2023-05-12 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 20:55 [Intel-gfx] [PATCH] drm/i1915/guc: Fix probe injection CI failures after recent change John.C.Harrison
2023-05-11 0:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-05-11 4:39 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-05-12 17:30 ` John Harrison
2023-05-12 10:17 ` Andi Shyti [this message]
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=ZF4SNE/XNXi75W5d@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=DRI-Devel@lists.freedesktop.org \
--cc=Intel-GFX@lists.freedesktop.org \
--cc=John.C.Harrison@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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