From: Taichi Nishimura <awkrail01@gmail.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
sumit.semwal@linaro.org, christian.koenig@amd.com
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linaro-mm-sig@lists.linaro.org, skhan@linuxfoundation.org,
Taichi Nishimura <awkrail01@gmail.com>
Subject: [PATCH] Fix drm documentation warning
Date: Wed, 8 Feb 2023 12:09:28 +0900 [thread overview]
Message-ID: <20230208030928.760176-1-awkrail01@gmail.com> (raw)
Sorry to re-send this patch again.
I forgot to attach description.
When running make htmldocs, I found that drm_accel_node
does not exist. The documents do not have any links to
acceleration nodes, so I removed them.
This patch is an extra credit for documentation task
in the Linux kernel Bug Fixing Spring unpaid 2023.
Best,
Taichi
Signed-off-by: Taichi Nishimura <awkrail01@gmail.com>
---
include/drm/drm_file.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/drm/drm_file.h b/include/drm/drm_file.h
index 0d1f853092ab..cffccf6b94de 100644
--- a/include/drm/drm_file.h
+++ b/include/drm/drm_file.h
@@ -407,8 +407,6 @@ static inline bool drm_is_render_client(const struct drm_file *file_priv)
*
* Returns true if this is an open file of the compute acceleration node, i.e.
* &drm_file.minor of @file_priv is a accel minor.
- *
- * See also the :ref:`section on accel nodes <drm_accel_node>`.
*/
static inline bool drm_is_accel_client(const struct drm_file *file_priv)
{
--
2.25.1
next reply other threads:[~2023-02-08 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 3:09 Taichi Nishimura [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-08 3:05 [PATCH] Fix drm documentation warning Taichi Nishimura
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=20230208030928.760176-1-awkrail01@gmail.com \
--to=awkrail01@gmail.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=sumit.semwal@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.