From: Thierry Reding <thierry.reding@kernel.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
simona@ffwll.ch, airlied@gmail.com, mperttunen@nvidia.com,
thierry.reding@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] gpu: host1x: fix missing 'host1x_context_device_bus_type'
Date: Thu, 28 May 2026 17:00:49 +0200 [thread overview]
Message-ID: <ahhYZtcmggWzUrbI@orome> (raw)
In-Reply-To: <20260123140512.609167-1-ben.dooks@codethink.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
On Fri, Jan 23, 2026 at 02:05:12PM +0000, Ben Dooks wrote:
> The drivers/gpu/host1x/context_bus.c does not include
> any declaration of host1x_context_device_bus_type, and
> after including "context.h" it also showed that there
> are two definitons in the kernel, so fix those two
>
> Fix by removing the definition in context.h and include
> <linux/host1x_context_bus.h> in context_bus.c
>
> Fixes the following sparse warning:
> drivers/gpu/host1x/context_bus.c:9:23: warning: symbol 'host1x_context_device_bus_type' was not declared. Should it be static?
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> --
> v2:
> - removed fixes line
> - changed to include into the c files directly
> ---
> drivers/gpu/host1x/context.c | 1 +
> drivers/gpu/host1x/context.h | 2 --
> drivers/gpu/host1x/context_bus.c | 1 +
> 3 files changed, 2 insertions(+), 2 deletions(-)
Applied this with Mikko's comments worked in. I also updated the commit
message a tiny bit and added a predeclaration of struct
host1x_memory_context in context.h out of an extra abundance of caution.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-05-28 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 14:05 [PATCH v2] gpu: host1x: fix missing 'host1x_context_device_bus_type' Ben Dooks
2026-01-24 1:20 ` Mikko Perttunen
2026-05-28 15:00 ` Thierry Reding [this message]
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=ahhYZtcmggWzUrbI@orome \
--to=thierry.reding@kernel.org \
--cc=airlied@gmail.com \
--cc=ben.dooks@codethink.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=simona@ffwll.ch \
--cc=thierry.reding@gmail.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