Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org,
	Arunpravin <Arunpravin.PaneerSelvam@amd.com>
Subject: Re: [Intel-gfx] [PATCH] drm/doc: pull in drm_buddy.c
Date: Wed, 9 Feb 2022 08:32:42 +0100	[thread overview]
Message-ID: <4dfd15b6-e402-f15d-f793-6d31e591fb20@amd.com> (raw)
In-Reply-To: <20220208151228.344997-1-matthew.auld@intel.com>

Am 08.02.22 um 16:12 schrieb Matthew Auld:
> Make sure we pull in the kernel-doc for this.
>
> Reported-by: Daniel Vetter <daniel@ffwll.ch>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Arunpravin <Arunpravin.PaneerSelvam@amd.com>
> Cc: Christian König <christian.koenig@amd.com>

Reviewed-by: Christian König <christian.koenig@amd.com>

> ---
>   Documentation/gpu/drm-mm.rst | 9 +++++++++
>   1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/gpu/drm-mm.rst b/Documentation/gpu/drm-mm.rst
> index 198bcc1affa1..f32ccce5722d 100644
> --- a/Documentation/gpu/drm-mm.rst
> +++ b/Documentation/gpu/drm-mm.rst
> @@ -466,6 +466,15 @@ DRM MM Range Allocator Function References
>   .. kernel-doc:: drivers/gpu/drm/drm_mm.c
>      :export:
>   
> +DRM Buddy Allocator
> +===================
> +
> +DRM Buddy Function References
> +-----------------------------
> +
> +.. kernel-doc:: drivers/gpu/drm/drm_buddy.c
> +   :export:
> +
>   DRM Cache Handling and Fast WC memcpy()
>   =======================================
>   


  parent reply	other threads:[~2022-02-09  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 15:12 [Intel-gfx] [PATCH] drm/doc: pull in drm_buddy.c Matthew Auld
2022-02-08 16:21 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-02-09  7:32 ` Christian König [this message]
2022-03-08 12:51   ` [Intel-gfx] [PATCH] " Matthew Auld
2022-03-08 13:10     ` Christian König

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=4dfd15b6-e402-f15d-f793-6d31e591fb20@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Arunpravin.PaneerSelvam@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.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