From: Greg KH <gregkh@linuxfoundation.org>
To: Akiyoshi Kurita <weibu@redadmin.org>
Cc: florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com,
umang.jain@ideasonboard.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vc04_services: mmal-vchiq: fix typo in comment
Date: Wed, 8 Oct 2025 12:34:27 +0200 [thread overview]
Message-ID: <2025100822-bobble-basics-137c@gregkh> (raw)
In-Reply-To: <20250923043617.2482243-1-weibu@redadmin.org>
On Tue, Sep 23, 2025 at 01:36:17PM +0900, Akiyoshi Kurita wrote:
> servie → service
>
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
> ---
> drivers/staging/vc04_services/vchiq-mmal/mmal-vchiq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/vc04_services/vchiq-mmal/mmal-vchiq.c b/drivers/staging/vc04_services/vchiq-mmal/mmal-vchiq.c
> index 3fe482bd2793..c2b5a37915f2 100644
> --- a/drivers/staging/vc04_services/vchiq-mmal/mmal-vchiq.c
> +++ b/drivers/staging/vc04_services/vchiq-mmal/mmal-vchiq.c
> @@ -326,7 +326,7 @@ static int bulk_receive(struct vchiq_mmal_instance *instance,
> * committed a buffer_to_host operation to the mmal
> * port without the buffer to back it up (underflow
> * handling) and there is no obvious way to deal with
> - * this - how is the mmal servie going to react when
> + * this - how is the mmal service going to react when
> * we fail to do the xfer and reschedule a buffer when
> * it arrives? perhaps a starved flag to indicate a
> * waiting bulk receive?
> --
> 2.47.3
>
>
Does not apply to the tree :(
prev parent reply other threads:[~2025-10-08 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 4:36 [PATCH] staging: vc04_services: mmal-vchiq: fix typo in comment Akiyoshi Kurita
2025-10-08 10:34 ` Greg KH [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=2025100822-bobble-basics-137c@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=umang.jain@ideasonboard.com \
--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).