From: Carlis <zhangxuezhi3@gmail.com>
To: gregkh@linuxfoundation.org, zhangxuezhi1@yulong.com
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH] staging: fbtft: fix a typo
Date: Fri, 26 Mar 2021 16:05:15 +0800 [thread overview]
Message-ID: <1616745915-194644-1-git-send-email-zhangxuezhi3@gmail.com> (raw)
From: "Carlis" <zhangxuezhi1@yulong.com>
Change 'tft' to 'TFT'
Signed-off-by: Carlis <zhangxuezhi1@yulong.com>
---
drivers/staging/fbtft/fbtft-core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fbtft-core.c b/drivers/staging/fbtft/fbtft-core.c
index 4f362da..44e7acb 100644
--- a/drivers/staging/fbtft/fbtft-core.c
+++ b/drivers/staging/fbtft/fbtft-core.c
@@ -775,7 +775,7 @@ void fbtft_framebuffer_release(struct fb_info *info)
EXPORT_SYMBOL(fbtft_framebuffer_release);
/**
- * fbtft_register_framebuffer - registers a tft frame buffer device
+ * fbtft_register_framebuffer - registers a TFT frame buffer device
* @fb_info: frame buffer info structure
*
* Sets SPI driverdata if needed
@@ -873,7 +873,7 @@ int fbtft_register_framebuffer(struct fb_info *fb_info)
EXPORT_SYMBOL(fbtft_register_framebuffer);
/**
- * fbtft_unregister_framebuffer - releases a tft frame buffer device
+ * fbtft_unregister_framebuffer - releases a TFT frame buffer device
* @fb_info: frame buffer info structure
*
* Frees SPI driverdata if needed
--
1.9.1
next reply other threads:[~2021-03-26 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 8:05 Carlis [this message]
2021-03-26 8:37 ` [PATCH] staging: fbtft: fix a typo Greg KH
2021-03-26 9:16 ` carlis
2021-03-26 9:33 ` Greg KH
2021-03-26 9:57 ` carlis
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=1616745915-194644-1-git-send-email-zhangxuezhi3@gmail.com \
--to=zhangxuezhi3@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=zhangxuezhi1@yulong.com \
/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).