All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alexandru Dadu" <alexandru.dadu@imgtec.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 3/5] drm/imagination: Make the RISC-V firmware header arch-independent
Date: Thu, 29 Oct 2026 06:34:15 +0000	[thread overview]
Message-ID: <sashiko-outbox-188823@kernel.org> (raw)
In-Reply-To: <20261029-prep-meta-fw-arch-independent-v2-3-b9f5d69b7a52@imgtec.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] drm/imagination: leftover pvr_rogue_riscv_internal.h after header rename
--

commit aa862385062c21d7cdb9dd94ddf176fd3c9475ba
Author: Alessio Belle <alessio.belle@imgtec.com>

drm/imagination: Make the RISC-V firmware header arch-independent

This commit introduces drivers/gpu/drm/imagination/pvr_fw_riscv_internal.h
with architecture-independent PVR_RISCV* definitions and updates
drivers/gpu/drm/imagination/pvr_fw_riscv.c to use them instead of the
ROGUE_RISCV* definitions from pvr_rogue_riscv_internal.h.

> diff --git a/drivers/gpu/drm/imagination/pvr_fw_riscv.c b/drivers/gpu/drm/imagination/pvr_fw_riscv.c
> index 0d4dd45520a9c..2b24c40bc20f9 100644
> --- a/drivers/gpu/drm/imagination/pvr_fw_riscv.c
> +++ b/drivers/gpu/drm/imagination/pvr_fw_riscv.c
> @@ -6,10 +6,10 @@
>  #include "pvr_fw_info.h"
>  #include "pvr_fw_mips.h"
>  #include "pvr_gem.h"
> +#define PVR_FW_RISCV_INTERNAL_H_EXPLICIT_INCLUDE
> +#include "pvr_fw_riscv_internal.h"
> +#undef PVR_FW_RISCV_INTERNAL_H_EXPLICIT_INCLUDE
>  #include "pvr_rogue_cr_defs.h"
> -#define PVR_ROGUE_RISCV_INTERNAL_H_EXPLICIT_INCLUDE
> -#include "pvr_rogue_riscv_internal.h"
> -#undef PVR_ROGUE_RISCV_INTERNAL_H_EXPLICIT_INCLUDE
>  #include "pvr_vm.h"

[ ... ]

> diff --git a/drivers/gpu/drm/imagination/pvr_fw_riscv_internal.h b/drivers/gpu/drm/imagination/pvr_fw_riscv_internal.h
> new file mode 100644
> index 0000000000000..abcbb4ef06fe1
> --- /dev/null
> +++ b/drivers/gpu/drm/imagination/pvr_fw_riscv_internal.h
> @@ -0,0 +1,43 @@
> +/* SPDX-License-Identifier: GPL-2.0 OR MIT */
> +/* Copyright (c) 2024 Imagination Technologies Ltd. */
> +
> +#ifndef PVR_FW_RISCV_INTERNAL_H
> +#define PVR_FW_RISCV_INTERNAL_H

[Severity: Low]
The commit message states that this patch renames both the header file and
its contents, and drivers/gpu/drm/imagination/pvr_fw_riscv.c (the sole user
of pvr_rogue_riscv_internal.h) is updated to include
pvr_fw_riscv_internal.h instead.

However, drivers/gpu/drm/imagination/pvr_fw_riscv_internal.h is added as a
new file while drivers/gpu/drm/imagination/pvr_rogue_riscv_internal.h
(guarded by PVR_ROGUE_RISCV_INTERNAL_H) is left behind in the tree with no
remaining users.

Should drivers/gpu/drm/imagination/pvr_rogue_riscv_internal.h be removed in
this commit as part of the rename?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261029-prep-meta-fw-arch-independent-v2-0-b9f5d69b7a52@imgtec.com?part=3

  reply	other threads:[~2026-10-29  6:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  6:29 [PATCH v2 0/5] drm/imagination: RISC-V and META firmware interface updates Alexandru Dadu
2026-10-29  6:29 ` Alexandru Dadu
2026-10-29  6:29 ` [PATCH v2 1/5] drm/imagination: Prepare heap config header for multi-arch support Alexandru Dadu
2026-10-29  6:29   ` Alexandru Dadu
2026-10-29  6:29 ` [PATCH v2 2/5] drm/imagination: Limit access to the RISC-V firmware interface Alexandru Dadu
2026-10-29  6:29   ` Alexandru Dadu
2026-10-29  6:29 ` [PATCH v2 3/5] drm/imagination: Make the RISC-V firmware header arch-independent Alexandru Dadu
2026-10-29  6:29   ` Alexandru Dadu
2026-10-29  6:34   ` sashiko-bot [this message]
2026-10-29  6:29 ` [PATCH v2 4/5] drm/imagination: Limit access to the META firmware interface Alexandru Dadu
2026-10-29  6:29   ` Alexandru Dadu
2026-10-29  6:34   ` sashiko-bot
2026-10-29  6:29 ` [PATCH v2 5/5] drm/imagination: Make the META firmware header arch-independent Alexandru Dadu
2026-10-29  6:29   ` Alexandru Dadu

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=sashiko-outbox-188823@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alexandru.dadu@imgtec.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.