The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: Rob Herring <robh@kernel.org>,
	Steven Price <steven.price@arm.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	kernel@collabora.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 7/8] drm/panfrost: Add forward declaration and types header
Date: Mon, 2 Dec 2024 12:21:14 +0100	[thread overview]
Message-ID: <20241202122114.61a4c2a9@collabora.com> (raw)
In-Reply-To: <20241128211223.1805830-8-adrian.larumbe@collabora.com>

On Thu, 28 Nov 2024 21:06:22 +0000
Adrián Larumbe <adrian.larumbe@collabora.com> wrote:

> This is to make LLVM syntactic analysers happy.
> 
> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>

Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>

> ---
>  drivers/gpu/drm/panfrost/panfrost_mmu.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/panfrost/panfrost_mmu.h b/drivers/gpu/drm/panfrost/panfrost_mmu.h
> index e6e6966a0cca..27c3c65ed074 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_mmu.h
> +++ b/drivers/gpu/drm/panfrost/panfrost_mmu.h
> @@ -4,6 +4,7 @@
>  #ifndef __PANFROST_MMU_H__
>  #define __PANFROST_MMU_H__
>  
> +struct panfrost_device;
>  struct panfrost_gem_mapping;
>  struct panfrost_file_priv;
>  struct panfrost_mmu;


  reply	other threads:[~2024-12-02 11:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 21:06 [PATCH v2 0/8] Some Panfrost fixes and improvements Adrián Larumbe
2024-11-28 21:06 ` [PATCH v2 1/8] drm/panfrost: Replace DRM driver allocation method with newer one Adrián Larumbe
2024-11-28 21:06 ` [PATCH v2 2/8] drm/panfrost: Handle inexistent GPU during probe Adrián Larumbe
2024-11-28 21:06 ` [PATCH v2 3/8] drm/panfrost: Handle job HW submit errors Adrián Larumbe
2024-12-02  9:21   ` Boris Brezillon
2024-12-02  9:24     ` Boris Brezillon
2024-11-28 21:06 ` [PATCH v2 4/8] drm/panfrost: Handle error when allocating AS number Adrián Larumbe
2024-12-02  9:29   ` Boris Brezillon
2024-11-28 21:06 ` [PATCH v2 5/8] drm/panfrost: Handle page mapping failure Adrián Larumbe
2024-12-02 11:14   ` Boris Brezillon
2024-11-28 21:06 ` [PATCH v2 6/8] drm/panfrost: Make re-enabling job interrupts at device reset optional Adrián Larumbe
2024-12-02 11:20   ` Boris Brezillon
2024-12-04 15:34     ` Adrián Larumbe
2024-12-04 16:40       ` Steven Price
2024-11-28 21:06 ` [PATCH v2 7/8] drm/panfrost: Add forward declaration and types header Adrián Larumbe
2024-12-02 11:21   ` Boris Brezillon [this message]
2024-11-28 21:06 ` [PATCH v2 8/8] drm/panfrost: Remove unused device property Adrián Larumbe
2024-12-02 11:23   ` Boris Brezillon

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=20241202122114.61a4c2a9@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=adrian.larumbe@collabora.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=steven.price@arm.com \
    --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