From: Alex Deucher <alexdeucher@gmail.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
DRI-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/drm_mm.h: Fix the name of the referenced function in comment
Date: Thu, 2 Nov 2017 00:02:50 -0400 [thread overview]
Message-ID: <CADnq5_NxJaWVYH-npy7JAbNKnb4sTsvjK5s1ARKH1PtZW3svGA@mail.gmail.com> (raw)
In-Reply-To: <20171101140445.2798-1-Liviu.Dudau@arm.com>
On Wed, Nov 1, 2017 at 10:04 AM, Liviu Dudau <Liviu.Dudau@arm.com> wrote:
> drm_mm_insert_node_generic() is a simplified version of
> drm_mm_insert_node_in_range(), update comment to reflect correct
> function name.
>
> Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> include/drm/drm_mm.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/drm/drm_mm.h b/include/drm/drm_mm.h
> index 8d10fc97801ce..101f566ae43d0 100644
> --- a/include/drm/drm_mm.h
> +++ b/include/drm/drm_mm.h
> @@ -386,7 +386,7 @@ int drm_mm_insert_node_in_range(struct drm_mm *mm,
> * @color: opaque tag value to use for this node
> * @mode: fine-tune the allocation search and placement
> *
> - * This is a simplified version of drm_mm_insert_node_in_range_generic() with no
> + * This is a simplified version of drm_mm_insert_node_in_range() with no
> * range restrictions applied.
> *
> * The preallocated node must be cleared to 0.
> --
> 2.14.3
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-02 4:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 14:04 [PATCH] drm/drm_mm.h: Fix the name of the referenced function in comment Liviu Dudau
2017-11-02 4:02 ` Alex Deucher [this message]
2017-11-02 9:46 ` Christian König
2017-11-02 13:15 ` Gustavo Padovan
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=CADnq5_NxJaWVYH-npy7JAbNKnb4sTsvjK5s1ARKH1PtZW3svGA@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=Liviu.Dudau@arm.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.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 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.