From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Akiyoshi Kurita <weibu@redadmin.org>
Cc: linux-staging@lists.linux.dev,
Florian Fainelli <florian.fainelli@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vc04_services: mmal: fix typo in comment
Date: Wed, 8 Oct 2025 12:35:12 +0200 [thread overview]
Message-ID: <2025100805-early-shindig-fc85@gregkh> (raw)
In-Reply-To: <20250918115619.1616818-1-weibu@redadmin.org>
On Thu, Sep 18, 2025 at 08:56:19PM +0900, Akiyoshi Kurita wrote:
> Correct a misspelling in a comment ("recived" -> "received").
>
> No functional change.
>
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
> ---
> drivers/staging/vc04_services/vchiq-mmal/mmal-msg.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/vc04_services/vchiq-mmal/mmal-msg.h b/drivers/staging/vc04_services/vchiq-mmal/mmal-msg.h
> index 471413248a14..1889494425eb 100644
> --- a/drivers/staging/vc04_services/vchiq-mmal/mmal-msg.h
> +++ b/drivers/staging/vc04_services/vchiq-mmal/mmal-msg.h
> @@ -13,7 +13,7 @@
>
> /*
> * all the data structures which serialise the MMAL protocol. note
> - * these are directly mapped onto the recived message data.
> + * these are directly mapped onto the received message data.
> *
> * BEWARE: They seem to *assume* pointers are u32 and that there is no
> * structure padding!
> --
> 2.47.3
>
Already sent by someone else before you, sorry :(
prev parent reply other threads:[~2025-10-08 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 11:56 [PATCH] staging: vc04_services: mmal: fix typo in comment Akiyoshi Kurita
2025-10-08 10:35 ` Greg Kroah-Hartman [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=2025100805-early-shindig-fc85@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.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).