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 0/2] accel/rocket: Fix build errors and sparse warning
Date: Sat, 02 Aug 2025 13:25:45 -0600 [thread overview]
Message-ID: <20250802-fix-rockchip-npu-build-v1-0-fb0f0dacb3fe@brighamcampbell.com> (raw)
Fix two build errors in rockchip NPU support code which were caused by
the integration of recent changes in the drm subsystem.
Fix a sparse warning regarding an undeclared const, rocket_pm_ops.
I tested these changes by enabling DRM_ACCEL_ROCKET and recompiling with
`make C=2`.
Signed-off-by: Brigham Campbell <me@brighamcampbell.com>
---
Brigham Campbell (2):
accel/rocket: Fix Rockchip NPU compilation
accel/rocket: Fix undeclared const rocket_pm_ops
drivers/accel/rocket/rocket_drv.h | 2 ++
drivers/accel/rocket/rocket_job.c | 4 ++--
2 files changed, 4 insertions(+), 2 deletions(-)
---
base-commit: 01ac6e4e53b6351df42c97d217b0d2dbeef5c917
change-id: 20250802-fix-rockchip-npu-build-ca759ba8da06
Best regards,
--
Brigham Campbell <me@brighamcampbell.com>
next 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 Brigham Campbell [this message]
2025-08-02 19:25 ` [PATCH 1/2] accel/rocket: Fix Rockchip NPU compilation Brigham Campbell
2025-08-02 19:25 ` [PATCH 2/2] accel/rocket: Fix undeclared const rocket_pm_ops Brigham Campbell
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-0-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).