From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>, kernel test robot <lkp@intel.com>
Subject: [PATCH] drm/xe: make xe_pm_runtime_lockdep_map a static struct
Date: Mon, 22 Apr 2024 16:14:54 -0400 [thread overview]
Message-ID: <20240422201454.699089-1-rodrigo.vivi@intel.com> (raw)
Fix the new sparse warning:
>> drivers/gpu/drm/xe/xe_pm.c:72:20: sparse: sparse: symbol
'xe_pm_runtime_lockdep_map' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202404191329.EZzOTzwK-lkp@intel.com/
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
drivers/gpu/drm/xe/xe_pm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_pm.c b/drivers/gpu/drm/xe/xe_pm.c
index 37fbeda12d3b..c1831106ea4b 100644
--- a/drivers/gpu/drm/xe/xe_pm.c
+++ b/drivers/gpu/drm/xe/xe_pm.c
@@ -69,7 +69,7 @@
*/
#ifdef CONFIG_LOCKDEP
-struct lockdep_map xe_pm_runtime_lockdep_map = {
+static struct lockdep_map xe_pm_runtime_lockdep_map = {
.name = "xe_pm_runtime_lockdep_map"
};
#endif
--
2.44.0
next reply other threads:[~2024-04-22 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 20:14 Rodrigo Vivi [this message]
2024-04-22 20:20 ` ✓ CI.Patch_applied: success for drm/xe: make xe_pm_runtime_lockdep_map a static struct Patchwork
2024-04-22 20:20 ` ✓ CI.checkpatch: " Patchwork
2024-04-22 20:21 ` ✓ CI.KUnit: " Patchwork
2024-04-22 20:32 ` [PATCH] " Gustavo Sousa
2024-04-22 20:33 ` ✓ CI.Build: success for " Patchwork
2024-04-22 20:35 ` ✓ CI.Hooks: " Patchwork
2024-04-22 20:37 ` ✓ CI.checksparse: " Patchwork
2024-04-23 4:22 ` ✗ CI.FULL: failure " Patchwork
2024-04-23 14:08 ` [PATCH] " Nilawar, Badal
2024-04-23 14:53 ` ✗ CI.Patch_applied: failure for drm/xe: make xe_pm_runtime_lockdep_map a static struct (rev2) 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=20240422201454.699089-1-rodrigo.vivi@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lkp@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