From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Jonathan Corbet <corbet@lwn.net>,
Steven Price <steven.price@arm.com>,
kernel@collabora.com, Stephen Rothwell <sfr@canb.auug.org.au>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/gpu: Fix Panthor documentation build warnings
Date: Wed, 30 Oct 2024 16:28:12 +0100 [thread overview]
Message-ID: <20241030162812.267750b6@collabora.com> (raw)
In-Reply-To: <20241009214346.2308917-1-adrian.larumbe@collabora.com>
On Wed, 9 Oct 2024 22:43:30 +0100
Adrián Larumbe <adrian.larumbe@collabora.com> wrote:
> Fix Panthor documentation build errors uncovered by the makedocs target
> when building with extra warnings enabled.
>
> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>
> Fixes: f25044688b04 ("drm/panthor: add sysfs knob for enabling job profiling")
Queued to drm-misc-next.
BTW, the commit hash was incorrect, please make sure you pick the hash
from the drm-misc tree not from your local branch next time.
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> Documentation/gpu/drivers.rst | 1 +
> Documentation/gpu/drm-usage-stats.rst | 1 +
> Documentation/gpu/panthor.rst | 2 +-
> 3 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/gpu/drivers.rst b/Documentation/gpu/drivers.rst
> index b899cbc5c2b4..7b1282e2d807 100644
> --- a/Documentation/gpu/drivers.rst
> +++ b/Documentation/gpu/drivers.rst
> @@ -22,6 +22,7 @@ GPU Driver Documentation
> afbc
> komeda-kms
> panfrost
> + panthor
>
> .. only:: subproject and html
>
> diff --git a/Documentation/gpu/drm-usage-stats.rst b/Documentation/gpu/drm-usage-stats.rst
> index a80f95ca1b2f..12ca3193bf15 100644
> --- a/Documentation/gpu/drm-usage-stats.rst
> +++ b/Documentation/gpu/drm-usage-stats.rst
> @@ -186,4 +186,5 @@ Driver specific implementations
>
> * :ref:`i915-usage-stats`
> * :ref:`panfrost-usage-stats`
> +* :ref:`panthor-usage-stats`
> * :ref:`xe-usage-stats`
> diff --git a/Documentation/gpu/panthor.rst b/Documentation/gpu/panthor.rst
> index cbf5c4429a2d..3f8979fa2b86 100644
> --- a/Documentation/gpu/panthor.rst
> +++ b/Documentation/gpu/panthor.rst
> @@ -4,7 +4,7 @@
> drm/Panthor CSF driver
> =========================
>
> -.. _panfrost-usage-stats:
> +.. _panthor-usage-stats:
>
> Panthor DRM client usage stats implementation
> ==============================================
prev parent reply other threads:[~2024-10-30 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 21:43 [PATCH] Documentation/gpu: Fix Panthor documentation build warnings Adrián Larumbe
2024-10-10 8:10 ` Steven Price
2024-10-30 15:28 ` Boris Brezillon [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=20241030162812.267750b6@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).