mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: simona@ffwll.ch, airlied@gmail.com, tzimmermann@suse.de,
	mripard@kernel.org, maarten.lankhorst@linux.intel.com,
	matt.coster@imgtec.com, frank.binns@imgtec.com,
	Ben Dooks <ben.dooks@codethink.co.uk>
Subject: [PATCH] drm/imagination: don't include pvr_rogue_fwif_check.h under sparse
Date: Mon, 12 Jan 2026 17:29:16 +0000	[thread overview]
Message-ID: <20260112172916.608949-1-ben.dooks@codethink.co.uk> (raw)

The checks in pvr_rogue_fwif_check.h trigger issues with sparse
as it may not decide to deal with structure definitions the same
way as the kernel.

There is nothing in pvr_rogue_fwif_check.h that needs to be checked
by sparse, so skip it to reduce the number of failed asserts from
sparse:

drivers/gpu/drm/imagination/pvr_rogue_fwif_check.h:487:1: error: static assertion failed: "struct rogue_fwif_hwrtdata is incorrect size"

Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
---
 drivers/gpu/drm/imagination/pvr_rogue_fwif.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/imagination/pvr_rogue_fwif.h b/drivers/gpu/drm/imagination/pvr_rogue_fwif.h
index 172886be4c82..1e4a74705e2f 100644
--- a/drivers/gpu/drm/imagination/pvr_rogue_fwif.h
+++ b/drivers/gpu/drm/imagination/pvr_rogue_fwif.h
@@ -2183,6 +2183,8 @@ struct rogue_fwif_hwrtdata {
 #define PVR_SYNC_CHECKPOINT_SIGNALED 0x519   /* Checkpoint has signaled. */
 #define PVR_SYNC_CHECKPOINT_ERRORED 0xeff    /* Checkpoint has been errored. */
 
+#ifndef __CHECKER__
 #include "pvr_rogue_fwif_check.h"
+#endif
 
 #endif /* PVR_ROGUE_FWIF_H */
-- 
2.37.2.352.g3c44437643


                 reply	other threads:[~2026-01-12 17:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260112172916.608949-1-ben.dooks@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=frank.binns@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matt.coster@imgtec.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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

all inboxes | Powered by JetHome®