From: Daniel Vetter <daniel@ffwll.ch>
To: Lyude <cpaul@redhat.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
David Airlie <airlied@linux.ie>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/fb_helper: Fix a few typos
Date: Wed, 4 May 2016 18:11:46 +0200 [thread overview]
Message-ID: <20160504161146.GD1286@phenom.ffwll.local> (raw)
In-Reply-To: <1462375734-8213-3-git-send-email-cpaul@redhat.com>
On Wed, May 04, 2016 at 11:28:53AM -0400, Lyude wrote:
> s/modest/modeset/
> s/aftert/after/
>
> Signed-off-by: Lyude <cpaul@redhat.com>
Applied to drm-misc, thanks.
-Daniel
> ---
> drivers/gpu/drm/drm_fb_helper.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
> index 15204c0..7778a0e 100644
> --- a/drivers/gpu/drm/drm_fb_helper.c
> +++ b/drivers/gpu/drm/drm_fb_helper.c
> @@ -2104,8 +2104,8 @@ out:
> * cmdline option.
> *
> * The other option is to just disable fbdev emulation since very likely the
> - * first modest from userspace will crash in the same way, and is even easier to
> - * debug. This can be done by setting the drm_kms_helper.fbdev_emulation=0
> + * first modeset from userspace will crash in the same way, and is even easier
> + * to debug. This can be done by setting the drm_kms_helper.fbdev_emulation=0
> * kernel cmdline option.
> *
> * RETURNS:
> @@ -2150,7 +2150,7 @@ EXPORT_SYMBOL(drm_fb_helper_initial_config);
> * hotplug interrupt).
> *
> * Note that drivers may call this even before calling
> - * drm_fb_helper_initial_config but only aftert drm_fb_helper_init. This allows
> + * drm_fb_helper_initial_config but only after drm_fb_helper_init. This allows
> * for a race-free fbcon setup and will make sure that the fbdev emulation will
> * not miss any hotplug events.
> *
> --
> 2.5.5
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2016-05-04 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 15:28 [PATCH 1/3] drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config() Lyude
2016-05-04 15:28 ` [PATCH 2/3] drm/fb_helper: Fix references to dev->mode_config.num_connector Lyude
2016-05-04 17:11 ` Daniel Vetter
2016-05-05 15:27 ` Lyude Paul
2016-05-04 15:28 ` [PATCH 3/3] drm/fb_helper: Fix a few typos Lyude
2016-05-04 16:11 ` Daniel Vetter [this message]
2016-05-04 16:17 ` [PATCH 1/3] drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config() Daniel Vetter
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=20160504161146.GD1286@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=cpaul@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox