From: "Cen Zhang (Microsoft)" <cenzhang@linux.microsoft.com>
To: Andy Shevchenko <andy@kernel.org>, Greg KH <gregkh@linuxfoundation.org>
Cc: Cen Zhang <cenzhang@linux.microsoft.com>,
Hungyu Lin <dennylin0707@gmail.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH] staging: fbtft: update outdated struct fbtft_ops comment
Date: Fri, 9 Oct 2026 11:45:26 -0400 [thread overview]
Message-ID: <20261009154526.43528-1-cenzhang@linux.microsoft.com> (raw)
Correct struct fbtft_ops outdated kernel-doc comment: 1) update
field write_reg to write_register; 2) remove non-existing field
free_gpios.
Signed-off-by: Cen Zhang (Microsoft) <cenzhang@linux.microsoft.com>
---
drivers/staging/fbtft/fbtft.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fbtft.h b/drivers/staging/fbtft/fbtft.h
index c7afb0fd3943..40a7567df1eb 100644
--- a/drivers/staging/fbtft/fbtft.h
+++ b/drivers/staging/fbtft/fbtft.h
@@ -37,7 +37,7 @@ struct fbtft_par;
* @write: Writes to interface bus
* @read: Reads from interface bus
* @write_vmem: Writes video memory to display
- * @write_reg: Writes to controller register
+ * @write_register: Writes to controller register
* @set_addr_win: Set the GRAM update window
* @reset: Reset the LCD controller
* @mkdirty: Marks display lines for update
@@ -46,7 +46,6 @@ struct fbtft_par;
* @blank: Blank the display (optional)
* @request_gpios_match: Do pinname to gpio matching
* @request_gpios: Request gpios from the kernel
- * @free_gpios: Free previously requested gpios
* @verify_gpios: Verify that necessary gpios is present (optional)
* @register_backlight: Used to register backlight device (optional)
* @unregister_backlight: Unregister backlight device (optional)
--
2.55.0
next reply other threads:[~2026-10-09 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 15:45 Cen Zhang (Microsoft) [this message]
2026-10-10 8:13 ` 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=20261009154526.43528-1-cenzhang@linux.microsoft.com \
--to=cenzhang@linux.microsoft.com \
--cc=andy@kernel.org \
--cc=dennylin0707@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 \
/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
all inboxes | Powered by JetHome®