[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20250923043617.2482243-1-weibu@redadmin.org>
Date: Tue, 23 Sep 2025 13:36:17 +0900
From: Akiyoshi Kurita <weibu@...admin.org>
To: gregkh@...uxfoundation.org
Cc: florian.fainelli@...adcom.com, bcm-kernel-feedback-list@...adcom.com,
umang.jain@...asonboard.com, linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org, Akiyoshi Kurita <weibu@...admin.org>
Subject: [PATCH] staging: vc04_services: mmal-vchiq: fix typo in comment
servie → service
Signed-off-by: Akiyoshi Kurita <weibu@...admin.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
Powered by blists - more mailing lists