linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: lijian_8010a29@163.com
To: FlorianSchandinat@gmx.de
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, lijian <lijian@yulong.com>
Subject: [PATCH] video: fbdev: via: dvi.c:  Fix a typo
Date: Thu,  3 Jun 2021 15:47:31 +0800	[thread overview]
Message-ID: <20210603074731.49717-1-lijian_8010a29@163.com> (raw)

From: lijian <lijian@yulong.com>

Change 'diplay' to 'display'.

Signed-off-by: lijian <lijian@yulong.com>
---
 drivers/video/fbdev/via/dvi.c | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/drivers/video/fbdev/via/dvi.c b/drivers/video/fbdev/via/dvi.c
index 13147e3066eb..ba1d9dbda99a 100644
--- a/drivers/video/fbdev/via/dvi.c
+++ b/drivers/video/fbdev/via/dvi.c
@@ -398,8 +398,10 @@ void viafb_dvi_enable(void)
 		if (viaparinfo->chip_info->gfx_chip_name == UNICHROME_CLE266)
 			tmds_register_write(0x88, 0x3b);
 		else
-			/*clear CR91[5] to direct on display period
-			   in the secondary diplay path */
+			/*
+			 * clear CR91[5] to direct on display period
+			 * in the secondary display path
+			 */
 			via_write_reg_mask(VIACR, 0x91, 0x00, 0x20);
 		break;
 
@@ -411,8 +413,10 @@ void viafb_dvi_enable(void)
 		if (viaparinfo->chip_info->gfx_chip_name == UNICHROME_CLE266)
 			tmds_register_write(0x88, 0x3b);
 		else
-			/*clear CR91[5] to direct on display period
-			  in the secondary diplay path */
+			/*
+			 * clear CR91[5] to direct on display period
+			 * in the secondary display path
+			 */
 			via_write_reg_mask(VIACR, 0x91, 0x00, 0x20);
 
 		/*fix DVI cannot enable on EPIA-M board */
-- 
2.25.1


                 reply	other threads:[~2021-06-03  7:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210603074731.49717-1-lijian_8010a29@163.com \
    --to=lijian_8010a29@163.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lijian@yulong.com \
    --cc=linux-fbdev@vger.kernel.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).