From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: Fix kerneldoc for DRM_MODE_PROP_IMMUTABLE
Date: Fri, 13 Jul 2018 18:51:36 +0300 [thread overview]
Message-ID: <20180713155136.GL5565@intel.com> (raw)
In-Reply-To: <20180713153444.95466-1-seanpaul@chromium.org>
On Fri, Jul 13, 2018 at 11:34:44AM -0400, Sean Paul wrote:
> Noticed this while browsing the docs.
>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> ---
> include/drm/drm_property.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/drm/drm_property.h b/include/drm/drm_property.h
> index 1d5c0b2a8956..c030f6ccab99 100644
> --- a/include/drm/drm_property.h
> +++ b/include/drm/drm_property.h
> @@ -147,10 +147,10 @@ struct drm_property {
> * properties are not exposed to legacy userspace.
> *
> * DRM_MODE_PROP_IMMUTABLE
> - * Set for properties where userspace cannot be changed by
> + * Set for properties whose values cannot be changed by
> * userspace. The kernel is allowed to update the value of these
> * properties. This is generally used to expose probe state to
> - * usersapce, e.g. the EDID, or the connector path property on DP
> + * userspace, e.g. the EDID, or the connector path property on DP
> * MST sinks.
> */
> uint32_t flags;
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
--
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-07-13 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 15:34 [PATCH] drm: Fix kerneldoc for DRM_MODE_PROP_IMMUTABLE Sean Paul
2018-07-13 15:51 ` Ville Syrjälä [this message]
2018-07-13 16:18 ` Sean Paul
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=20180713155136.GL5565@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=seanpaul@chromium.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.