From: Julia Lawall <julia.lawall@inria.fr>
To: Shivani Patel <patelshivani2283@gmail.com>
Cc: outreachy@lists.linux.dev, Andy Shevchenko <andy@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: fix spelling mistake "writte" -> "written"
Date: Mon, 9 Nov 2026 15:21:11 +0100 (CET) [thread overview]
Message-ID: <e235fcb8-c0fd-1e63-eddf-41efd70c7c4@inria.fr> (raw)
In-Reply-To: <20261109133731.66016-1-patelshivani2283@gmail.com>
On Mon, 9 Nov 2026, Shivani Patel wrote:
> Correct spelling mistake in comment ("writte" -> "written").
>
> Signed-off-by: Shivani Patel <patelshivani2283@gmail.com>
Someone else has already submitted that patch. Please check the mailing
list archive before submitting patches.
julia
> ---
> drivers/staging/fbtft/fb_st7789v.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/fbtft/fb_st7789v.c b/drivers/staging/fbtft/fb_st7789v.c
> index 861a15414..c4db681eb 100644
> --- a/drivers/staging/fbtft/fb_st7789v.c
> +++ b/drivers/staging/fbtft/fb_st7789v.c
> @@ -221,7 +221,7 @@ static int init_display(struct fbtft_par *par)
> * write_vmem() - write data to display.
> * @par: FBTFT parameter object.
> * @offset: offset from screen_buffer.
> - * @len: the length of data to be writte.
> + * @len: the length of data to be written.
> *
> * Return: 0 on success, or a negative error code otherwise.
> */
> --
> 2.50.1 (Apple Git-155)
>
>
>
next prev parent reply other threads:[~2026-11-09 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 13:37 [PATCH] staging: fbtft: fix spelling mistake "writte" -> "written" Shivani Patel
2026-11-09 14:21 ` Julia Lawall [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-03 22:11 Eileen Blessing Kabi
2026-11-04 8:56 ` 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=e235fcb8-c0fd-1e63-eddf-41efd70c7c4@inria.fr \
--to=julia.lawall@inria.fr \
--cc=andy@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=patelshivani2283@gmail.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