All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
	<badal.nilawar@intel.com>, <jonathan.cavitt@intel.com>
Subject: Re: [PATCH v3 1/2] drm/xe/xe_survivability: Use static for survivability info attributes
Date: Fri, 19 Dec 2025 10:57:44 -0500	[thread overview]
Message-ID: <aUV1-IBqkOH4ASDP@intel.com> (raw)
In-Reply-To: <20251219105224.871930-5-riana.tauro@intel.com>

On Fri, Dec 19, 2025 at 04:22:26PM +0530, Riana Tauro wrote:
> Fix sparse warnings. Use static for survivability info attributes.
> 
> Fixes: f4e9fc967afd ("drm/xe/xe_survivability: Redesign survivability mode")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202512101919.G12cuhBJ-lkp@intel.com/
> Signed-off-by: Riana Tauro <riana.tauro@intel.com>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_survivability_mode.c | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_survivability_mode.c b/drivers/gpu/drm/xe/xe_survivability_mode.c
> index 7520d7b7f9b8..e6e326dfb92b 100644
> --- a/drivers/gpu/drm/xe/xe_survivability_mode.c
> +++ b/drivers/gpu/drm/xe/xe_survivability_mode.c
> @@ -228,15 +228,15 @@ static ssize_t survivability_info_show(struct device *dev,
>  		.index = _index,						\
>  	}
>  
> -SURVIVABILITY_ATTR_RO(capability_info, CAPABILITY_INFO);
> -SURVIVABILITY_ATTR_RO(postcode_trace, POSTCODE_TRACE);
> -SURVIVABILITY_ATTR_RO(postcode_trace_overflow, POSTCODE_TRACE_OVERFLOW);
> -SURVIVABILITY_ATTR_RO(aux_info0, AUX_INFO0);
> -SURVIVABILITY_ATTR_RO(aux_info1, AUX_INFO1);
> -SURVIVABILITY_ATTR_RO(aux_info2, AUX_INFO2);
> -SURVIVABILITY_ATTR_RO(aux_info3, AUX_INFO3);
> -SURVIVABILITY_ATTR_RO(aux_info4, AUX_INFO4);
> -SURVIVABILITY_ATTR_RO(fdo_mode, FDO_INFO);
> +static SURVIVABILITY_ATTR_RO(capability_info, CAPABILITY_INFO);
> +static SURVIVABILITY_ATTR_RO(postcode_trace, POSTCODE_TRACE);
> +static SURVIVABILITY_ATTR_RO(postcode_trace_overflow, POSTCODE_TRACE_OVERFLOW);
> +static SURVIVABILITY_ATTR_RO(aux_info0, AUX_INFO0);
> +static SURVIVABILITY_ATTR_RO(aux_info1, AUX_INFO1);
> +static SURVIVABILITY_ATTR_RO(aux_info2, AUX_INFO2);
> +static SURVIVABILITY_ATTR_RO(aux_info3, AUX_INFO3);
> +static SURVIVABILITY_ATTR_RO(aux_info4, AUX_INFO4);
> +static SURVIVABILITY_ATTR_RO(fdo_mode, FDO_INFO);
>  
>  static void xe_survivability_mode_fini(void *arg)
>  {
> -- 
> 2.47.1
> 

  reply	other threads:[~2025-12-19 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 10:52 [PATCH v3 0/2] Survivability mode fixes Riana Tauro
2025-12-19 10:52 ` [PATCH v3 1/2] drm/xe/xe_survivability: Use static for survivability info attributes Riana Tauro
2025-12-19 15:57   ` Rodrigo Vivi [this message]
2025-12-19 10:52 ` [PATCH v3 2/2] drm/xe/xe_survivability: Add index bound check Riana Tauro
2025-12-19 15:59   ` Rodrigo Vivi
2025-12-19 11:11 ` ✓ CI.KUnit: success for Survivability mode fixes (rev3) Patchwork
2025-12-19 12:20 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-20 13:25 ` ✗ Xe.CI.Full: 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=aUV1-IBqkOH4ASDP@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=riana.tauro@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.