From: Preetish Amballi <amballip@gmail.com>
To: andy@kernel.org, gregkh@linuxfoundation.org
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Preetish Amballi <amballip@gmail.com>
Subject: [PATCH] staging: fbtft: Fix wrong controller name in fb_bd663474
Date: Sun, 9 Aug 2026 11:02:53 +0530 [thread overview]
Message-ID: <20260809053253.14537-1-amballip@gmail.com> (raw)
The file fb_bd663474.c is a driver for the BD663474 LCD controller,
but the comment header and MODULE_DESCRIPTION incorrectly reference
'uPD161704' — a copy-paste error from fb_upd161704.c.
Fix the comment and MODULE_DESCRIPTION to say 'BD663474' instead of
'uPD161704'.
Signed-off-by: Preetish Amballi <amballip@gmail.com>
---
drivers/staging/fbtft/fb_bd663474.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fb_bd663474.c b/drivers/staging/fbtft/fb_bd663474.c
index 1629c2c440a9..c34f859043ef 100644
--- a/drivers/staging/fbtft/fb_bd663474.c
+++ b/drivers/staging/fbtft/fb_bd663474.c
@@ -1,6 +1,6 @@
// SPDX-License-Identifier: GPL-2.0+
/*
- * FB driver for the uPD161704 LCD Controller
+ * FB driver for the BD663474 LCD Controller
*
* Copyright (C) 2014 Seong-Woo Kim
*
@@ -166,6 +166,6 @@ MODULE_ALIAS("platform:" DRVNAME);
MODULE_ALIAS("spi:bd663474");
MODULE_ALIAS("platform:bd663474");
-MODULE_DESCRIPTION("FB driver for the uPD161704 LCD Controller");
+MODULE_DESCRIPTION("FB driver for the BD663474 LCD Controller");
MODULE_AUTHOR("Seong-Woo Kim");
MODULE_LICENSE("GPL");
--
2.43.0
next reply other threads:[~2026-08-09 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 5:32 Preetish Amballi [this message]
2026-08-10 7:06 ` [PATCH] staging: fbtft: Fix wrong controller name in fb_bd663474 Andy Shevchenko
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=20260809053253.14537-1-amballip@gmail.com \
--to=amballip@gmail.com \
--cc=andy@kernel.org \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.