From: Brigham Campbell <me@brighamcampbell.com>
To: Tomeu Vizoso <tomeu@tomeuvizoso.net>, Oded Gabbay <ogabbay@kernel.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
Brigham Campbell <me@brighamcampbell.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH 2/2] accel/rocket: Fix undeclared const rocket_pm_ops
Date: Sat, 02 Aug 2025 13:25:47 -0600 [thread overview]
Message-ID: <20250802-fix-rockchip-npu-build-v1-2-fb0f0dacb3fe@brighamcampbell.com> (raw)
In-Reply-To: <20250802-fix-rockchip-npu-build-v1-0-fb0f0dacb3fe@brighamcampbell.com>
Fix sparse warning regarding an undeclared const rocket_pm_ops, which is
used in rocket_drv.c.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202508030021.uwdr4P08-lkp@intel.com/
Signed-off-by: Brigham Campbell <me@brighamcampbell.com>
---
drivers/accel/rocket/rocket_drv.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/accel/rocket/rocket_drv.h b/drivers/accel/rocket/rocket_drv.h
index f50634935b605c542cce16a2b91c1e43ec16bc81..2c673bb99ccc1d90e2dafdc89e9a5c6df216a309 100644
--- a/drivers/accel/rocket/rocket_drv.h
+++ b/drivers/accel/rocket/rocket_drv.h
@@ -9,6 +9,8 @@
#include "rocket_device.h"
+extern const struct dev_pm_ops rocket_pm_ops;
+
struct rocket_iommu_domain {
struct iommu_domain *domain;
struct kref kref;
--
2.50.1
next prev parent reply other threads:[~2025-08-02 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-02 19:25 [PATCH 0/2] accel/rocket: Fix build errors and sparse warning Brigham Campbell
2025-08-02 19:25 ` [PATCH 1/2] accel/rocket: Fix Rockchip NPU compilation Brigham Campbell
2025-08-02 19:25 ` Brigham Campbell [this message]
2025-08-03 15:33 ` [PATCH 0/2] accel/rocket: Fix build errors and sparse warning Tomeu Vizoso
2025-08-03 16:14 ` Brigham Campbell
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=20250802-fix-rockchip-npu-build-v1-2-fb0f0dacb3fe@brighamcampbell.com \
--to=me@brighamcampbell.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ogabbay@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tomeu@tomeuvizoso.net \
/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;
as well as URLs for NNTP newsgroup(s).