From: Dan Carpenter <dan.carpenter@linaro.org>
To: Akiyoshi Kurita <weibu@redadmin.org>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: rtl8723bs: fix typo in comment
Date: Fri, 12 Sep 2025 11:26:45 +0300 [thread overview]
Message-ID: <aMPZRUm9vHWQ0_pe@stanley.mountain> (raw)
In-Reply-To: <20250912064406.707039-1-weibu@redadmin.org>
On Fri, Sep 12, 2025 at 03:44:06PM +0900, Akiyoshi Kurita wrote:
> Fix a misspelling in a header comment: "configurtions" -> "configurations".
>
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
> ---
> v4:
> - Correct reversed diff.
> - Drop "No functional change." per review.
>
There you go. :)
Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>
regards,
dan carpenter
prev parent reply other threads:[~2025-09-12 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 2:28 [PATCH v2] staging: rtl8723bs: fix typo in comment Akiyoshi Kurita
2025-09-12 5:32 ` Greg KH
2025-09-12 6:44 ` [PATCH v4] " Akiyoshi Kurita
2025-09-12 8:26 ` Dan Carpenter [this message]
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=aMPZRUm9vHWQ0_pe@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=weibu@redadmin.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).