From: John Harrison <john.c.harrison@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-xe <intel-xe@lists.freedesktop.org>
Cc: Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [PATCH 1/2] drm/xe/uc: Remove static from loop variable
Date: Thu, 20 Mar 2025 13:08:19 -0700 [thread overview]
Message-ID: <f24020f6-b6ac-4a1b-8f4d-75574582d726@intel.com> (raw)
In-Reply-To: <20250307-xe-per-gt-fw-v1-1-459574d76400@intel.com>
On 3/7/2025 10:13 AM, Lucas De Marchi wrote:
> The `entries` variable is used to loop through the array - it's supposed
> to be const, but not static.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/xe/xe_uc_fw.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
> index 18e06ee9e23fc..c22da0ce9fb0d 100644
> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
> @@ -225,8 +225,8 @@ uc_fw_auto_select(struct xe_device *xe, struct xe_uc_fw *uc_fw)
> [XE_UC_FW_TYPE_HUC] = { entries_huc, ARRAY_SIZE(entries_huc) },
> [XE_UC_FW_TYPE_GSC] = { entries_gsc, ARRAY_SIZE(entries_gsc) },
> };
> - static const struct uc_fw_entry *entries;
> enum xe_platform p = xe->info.platform;
> + const struct uc_fw_entry *entries;
> u32 count;
> int i;
>
>
next prev parent reply other threads:[~2025-03-20 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 18:13 [PATCH 0/2] drm/xe: Support different GuCs per GT Lucas De Marchi
2025-03-07 18:13 ` [PATCH 1/2] drm/xe/uc: Remove static from loop variable Lucas De Marchi
2025-03-20 20:08 ` John Harrison [this message]
2025-03-07 18:13 ` [PATCH 2/2] drm/xe/uc: Add support for different firmware files on each GT Lucas De Marchi
2025-03-20 20:09 ` John Harrison
2025-03-07 20:01 ` ✓ CI.Patch_applied: success for drm/xe: Support different GuCs per GT Patchwork
2025-03-07 20:01 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-07 20:02 ` ✓ CI.KUnit: success " Patchwork
2025-03-07 20:19 ` ✓ CI.Build: " Patchwork
2025-03-07 20:21 ` ✓ CI.Hooks: " Patchwork
2025-03-07 20:23 ` ✓ CI.checksparse: " Patchwork
2025-03-07 20:45 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-09 0:37 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-20 20:09 ` [PATCH 0/2] " John Harrison
2025-03-21 18:42 ` Lucas De Marchi
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=f24020f6-b6ac-4a1b-8f4d-75574582d726@intel.com \
--to=john.c.harrison@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@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