From: Dylan Le <self@dylanle.dev>
To: 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>
Cc: Dylan Le <self@dylanle.dev>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: [PATCH] Documentation: gpu: add acceleration node section
Date: Thu, 23 Feb 2023 02:52:52 +0000 [thread overview]
Message-ID: <7799513f0fb5aee27b64752c037980471be669c5.1677120686.git.self@dylanle.dev> (raw)
This patch was initially written for the Linux Kernel Bug Fixing Mentorship
program. The patch adds a temporarily stubbed section on Acceleration Nodes
to resolve a documentation warning.
This resolves the warning:
./Documentation/gpu/drm-internals:179: ./include/drm/drm_file.h:411: WARNING: undefined label: drm_accel_node
I would appreciate any feedback on what should be documented here.
Signed-off-by: Dylan Le <self@dylanle.dev>
---
Documentation/gpu/drm-uapi.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index ce47b4292..d25539862 100644
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -175,6 +175,15 @@ other hand, a driver requires shared state between clients which is
visible to user-space and accessible beyond open-file boundaries, they
cannot support render nodes.
+.. _drm_accel_node:
+
+Acceleration nodes
+==================
+
+.. note::
+ There is not any documentation yet need to figure out what this is.
+
+
Device Hot-Unplug
=================
--
2.30.2
next reply other threads:[~2023-02-23 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 2:52 Dylan Le [this message]
2023-02-23 4:25 ` [PATCH] Documentation: gpu: add acceleration node section Bagas Sanjaya
2023-02-27 16:43 ` Jeffrey Hugo
2023-02-28 7:59 ` Bagas Sanjaya
2023-03-03 14:49 ` Dylan Le
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=7799513f0fb5aee27b64752c037980471be669c5.1677120686.git.self@dylanle.dev \
--to=self@dylanle.dev \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=skhan@linuxfoundation.org \
--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