From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: David Airlie <airlied@linux.ie>,
Randy Dunlap <rdunlap@infradead.org>,
dri-devel@lists.freedesktop.org
Subject: [PATCH 1/7] drm: drm_atomic.h: delete duplicated word in comment
Date: Tue, 14 Jul 2020 22:23:43 -0700 [thread overview]
Message-ID: <20200715052349.23319-1-rdunlap@infradead.org> (raw)
Drop doubled word "than" in a comment.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org
---
include/drm/drm_atomic.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20200714.orig/include/drm/drm_atomic.h
+++ linux-next-20200714/include/drm/drm_atomic.h
@@ -103,7 +103,7 @@ struct drm_crtc_commit {
*
* Will be signalled when all hw register changes for this commit have
* been written out. Especially when disabling a pipe this can be much
- * later than than @flip_done, since that can signal already when the
+ * later than @flip_done, since that can signal already when the
* screen goes black, whereas to fully shut down a pipe more register
* I/O is required.
*
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-07-15 7:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 5:23 Randy Dunlap [this message]
2020-07-15 5:23 ` [PATCH 2/7] drm: drm_bridge.h: delete duplicated word in comment Randy Dunlap
2020-07-15 5:23 ` [PATCH 3/7] drm: drm_gem.h: delete duplicated words in comments Randy Dunlap
2020-07-15 5:23 ` [PATCH 4/7] drm: drm_mode_config.h: " Randy Dunlap
2020-07-15 5:23 ` [PATCH 5/7] drm: i915_drm.h: " Randy Dunlap
2020-07-15 5:23 ` [PATCH 6/7] drm: msm_drm.h: " Randy Dunlap
2020-07-15 5:23 ` [PATCH 7/7] drm: drm_rect.h: delete duplicated word in comment Randy Dunlap
2020-07-15 12:03 ` [PATCH 1/7] drm: drm_atomic.h: " 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=20200715052349.23319-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=airlied@linux.ie \
--cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).