From: Jani Nikula <jani.nikula@intel.com>
To: Markus Schneider-Pargmann <msp@baylibre.com>
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] doc: gpu: drm-internals: Create reference to DRM mm
Date: Tue, 21 Sep 2021 12:58:06 +0300 [thread overview]
Message-ID: <87ilyutfm9.fsf@intel.com> (raw)
In-Reply-To: <20210920140326.ygodeun2qokb6wcw@blmsp>
On Mon, 20 Sep 2021, Markus Schneider-Pargmann <msp@baylibre.com> wrote:
> Hi Jani,
>
> On Mon, Sep 20, 2021 at 02:01:57PM +0300, Jani Nikula wrote:
>> On Mon, 20 Sep 2021, Markus Schneider-Pargmann <msp@baylibre.com> wrote:
>> > 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.
>>
>> Please use rst references instead of a file reference.
>
> Thanks for your comment. Could you please explain it a bit more to me?
>
> I am new to the kernel sphinx documentation so I looked it up in
> Documentation/doc-guide/sphinx.rst 'Cross-referencing'. It is listed as
> the preferred way to reference other documents if I understand it
> correctly.
>
> Should the doc-guide be updated then if a rst reference is preferred?
Please go with what the doc-guide says, sorry for the noise.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2021-09-21 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 10:13 [PATCH] doc: gpu: drm-internals: Create reference to DRM mm Markus Schneider-Pargmann
2021-09-20 11:01 ` Jani Nikula
2021-09-20 14:03 ` Markus Schneider-Pargmann
2021-09-21 9:58 ` Jani Nikula [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=87ilyutfm9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=msp@baylibre.com \
/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