From: Daniel Vetter <daniel@ffwll.ch>
To: Antonio Borneo <antonio.borneo@st.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH] drm/connector: fix minor typos in comments
Date: Mon, 29 Jun 2020 10:33:58 +0200 [thread overview]
Message-ID: <20200629083358.GK3278063@phenom.ffwll.local> (raw)
In-Reply-To: <20200626204252.44565-1-antonio.borneo@st.com>
On Fri, Jun 26, 2020 at 10:42:52PM +0200, Antonio Borneo wrote:
> Some of these comments are part of the Linux GPU Driver Developer's
> Guide.
> Fix some minor typo in the comments and remove a repeated 'the'.
>
> Signed-off-by: Antonio Borneo <antonio.borneo@st.com>
Queued up for 5.9 in drm-misc-next, thanks for your patch.
-Daniel
> ---
> drivers/gpu/drm/drm_connector.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
> index d877ddc6dc57..cb62fb8e594e 100644
> --- a/drivers/gpu/drm/drm_connector.c
> +++ b/drivers/gpu/drm/drm_connector.c
> @@ -38,7 +38,7 @@
> * DOC: overview
> *
> * In DRM connectors are the general abstraction for display sinks, and include
> - * als fixed panels or anything else that can display pixels in some form. As
> + * also fixed panels or anything else that can display pixels in some form. As
> * opposed to all other KMS objects representing hardware (like CRTC, encoder or
> * plane abstractions) connectors can be hotplugged and unplugged at runtime.
> * Hence they are reference-counted using drm_connector_get() and
> @@ -129,7 +129,7 @@ EXPORT_SYMBOL(drm_get_connector_type_name);
>
> /**
> * drm_connector_get_cmdline_mode - reads the user's cmdline mode
> - * @connector: connector to quwery
> + * @connector: connector to query
> *
> * The kernel supports per-connector configuration of its consoles through
> * use of the video= parameter. This function parses that option and
> @@ -991,7 +991,7 @@ static const struct drm_prop_enum_list dp_colorspaces[] = {
> * DP MST sinks), or high-res integrated panels (like dual-link DSI) which
> * are not gen-locked. Note that for tiled panels which are genlocked, like
> * dual-link LVDS or dual-link DSI, the driver should try to not expose the
> - * tiling and virtualize both &drm_crtc and &drm_plane if needed. Drivers
> + * tiling and virtualise both &drm_crtc and &drm_plane if needed. Drivers
> * should update this value using drm_connector_set_tile_property().
> * Userspace cannot change this property.
> * link-status:
> @@ -1131,7 +1131,7 @@ static const struct drm_prop_enum_list dp_colorspaces[] = {
> *
> * It will even need to do colorspace conversion and get all layers
> * to one common colorspace for blending. It can use either GL, Media
> - * or display engine to get this done based on the capabilties of the
> + * or display engine to get this done based on the capabilities of the
> * associated hardware.
> *
> * Driver expects metadata to be put in &struct hdr_output_metadata
> @@ -1614,7 +1614,7 @@ EXPORT_SYMBOL(drm_mode_create_scaling_mode_property);
> * variable refresh rate capability for a connector.
> *
> * Returns:
> - * Zero on success, negative errono on failure.
> + * Zero on success, negative errno on failure.
> */
> int drm_connector_attach_vrr_capable_property(
> struct drm_connector *connector)
> @@ -1759,7 +1759,7 @@ EXPORT_SYMBOL(drm_mode_create_aspect_ratio_property);
> * HDMI connectors.
> *
> * Returns:
> - * Zero on success, negative errono on failure.
> + * Zero on success, negative errno on failure.
> */
> int drm_mode_create_hdmi_colorspace_property(struct drm_connector *connector)
> {
> @@ -1788,7 +1788,7 @@ EXPORT_SYMBOL(drm_mode_create_hdmi_colorspace_property);
> * DP connectors.
> *
> * Returns:
> - * Zero on success, negative errono on failure.
> + * Zero on success, negative errno on failure.
> */
> int drm_mode_create_dp_colorspace_property(struct drm_connector *connector)
> {
> @@ -1840,7 +1840,7 @@ EXPORT_SYMBOL(drm_mode_create_content_type_property);
> * drm_mode_create_suggested_offset_properties - create suggests offset properties
> * @dev: DRM device
> *
> - * Create the the suggested x/y offset property for connectors.
> + * Create the suggested x/y offset property for connectors.
> */
> int drm_mode_create_suggested_offset_properties(struct drm_device *dev)
> {
> @@ -1963,7 +1963,7 @@ int drm_connector_update_edid_property(struct drm_connector *connector,
> size = EDID_LENGTH * (1 + edid->extensions);
>
> /* Set the display info, using edid if available, otherwise
> - * reseting the values to defaults. This duplicates the work
> + * resetting the values to defaults. This duplicates the work
> * done in drm_add_edid_modes, but that function is not
> * consistently called before this one in all drivers and the
> * computation is cheap enough that it seems better to
> @@ -2076,7 +2076,7 @@ void drm_connector_set_vrr_capable_property(
> EXPORT_SYMBOL(drm_connector_set_vrr_capable_property);
>
> /**
> - * drm_connector_set_panel_orientation - sets the connecter's panel_orientation
> + * drm_connector_set_panel_orientation - sets the connector's panel_orientation
> * @connector: connector for which to set the panel-orientation property.
> * @panel_orientation: drm_panel_orientation value to set
> *
> @@ -2131,7 +2131,7 @@ EXPORT_SYMBOL(drm_connector_set_panel_orientation);
>
> /**
> * drm_connector_set_panel_orientation_with_quirk -
> - * set the connecter's panel_orientation after checking for quirks
> + * set the connector's panel_orientation after checking for quirks
> * @connector: connector for which to init the panel-orientation property.
> * @panel_orientation: drm_panel_orientation value to set
> * @width: width in pixels of the panel, used for panel quirk detection
> --
> 2.27.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2020-06-29 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 20:42 Antonio Borneo
2020-06-29 8:33 ` 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=20200629083358.GK3278063@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=antonio.borneo@st.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®