From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
Markus Schneider-Pargmann <msp@baylibre.com>,
Jani Nikula <jani.nikula@intel.com>
Subject: [PATCH] doc: gpu: drm-internals: Create reference to DRM mm
Date: Mon, 20 Sep 2021 12:13:34 +0200 [thread overview]
Message-ID: <20210920101334.249832-1-msp@baylibre.com> (raw)
This short sentence references nothing for details about memory manager.
Replace it with the documentation file for DRM memory management.
Cc: Jani Nikula <jani.nikula@intel.com>
Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
---
Documentation/gpu/drm-internals.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/gpu/drm-internals.rst b/Documentation/gpu/drm-internals.rst
index 06af044c882f..bdcdfc4ede04 100644
--- a/Documentation/gpu/drm-internals.rst
+++ b/Documentation/gpu/drm-internals.rst
@@ -126,8 +126,8 @@ Memory Manager Initialization
Every DRM driver requires a memory manager which must be initialized at
load time. DRM currently contains two memory managers, the Translation
Table Manager (TTM) and the Graphics Execution Manager (GEM). This
-document describes the use of the GEM memory manager only. See ? for
-details.
+document describes the use of the GEM memory manager only. See
+Documentation/gpu/drm-mm.rst for details.
Miscellaneous Device Configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
2.33.0
next reply other threads:[~2021-09-20 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 10:13 Markus Schneider-Pargmann [this message]
2021-09-20 11:01 ` [PATCH] doc: gpu: drm-internals: Create reference to DRM mm Jani Nikula
2021-09-20 14:03 ` Markus Schneider-Pargmann
2021-09-21 9:58 ` Jani Nikula
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=20210920101334.249832-1-msp@baylibre.com \
--to=msp@baylibre.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
/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