From: Daniel Vetter <daniel@ffwll.ch>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: use the right function name in documentation
Date: Mon, 10 Oct 2016 11:24:23 +0200 [thread overview]
Message-ID: <20161010092423.GU20761@phenom.ffwll.local> (raw)
In-Reply-To: <1476032820-3275-1-git-send-email-notasas@gmail.com>
On Sun, Oct 09, 2016 at 08:07:00PM +0300, Grazvydas Ignotas wrote:
> There is no late_unregister(), it looks like the comment meant
> late_register(). Also fix a typo while at it.
>
> Signed-off-by: Grazvydas Ignotas <notasas@gmail.com>
Applied to drm-misc, thanks.
-Daniel
> ---
> include/drm/drm_connector.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
> index 51a15de..43c5cd7 100644
> --- a/include/drm/drm_connector.h
> +++ b/include/drm/drm_connector.h
> @@ -345,7 +345,7 @@ struct drm_connector_funcs {
> *
> * This optional hook should be used to unregister the additional
> * userspace interfaces attached to the connector from
> - * late_unregister(). It is called from drm_connector_unregister(),
> + * late_register(). It is called from drm_connector_unregister(),
> * early in the driver unload sequence to disable userspace access
> * before data structures are torndown.
> */
> @@ -365,7 +365,7 @@ struct drm_connector_funcs {
> * @atomic_duplicate_state:
> *
> * Duplicate the current atomic state for this connector and return it.
> - * The core and helpers gurantee that any atomic state duplicated with
> + * The core and helpers guarantee that any atomic state duplicated with
> * this hook and still owned by the caller (i.e. not transferred to the
> * driver by calling ->atomic_commit() from struct
> * &drm_mode_config_funcs) will be cleaned up by calling the
> --
> 2.7.4
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-10-10 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 17:07 [PATCH] drm: use the right function name in documentation Grazvydas Ignotas
2016-10-10 9:24 ` Daniel Vetter [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=20161010092423.GU20761@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=notasas@gmail.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