Re: [PATCH] docs: media: fix spelling errors

[Sakari Ailus]

Hi,

Please use Documentation: prefix for patches under Documentation/.

On Sun, Jul 26, 2026 at 12:24:07PM +0530, shaikh.kamal wrote:
> Fix spelling errors reported by codespell:
> 
>   thare -> there  (vidioc-subdev-g-routing.rst)
>   stuct -> struct (legacy_dvb_video.rst)
> 
> No functional change.
> 
> Signed-off-by: shaikh.kamal <shaikhkamal2012@xxxxxxxxx>

Does this conform to the spelling of your name? Just confirming.

It needs to match From: nonetheless.

> ---
>  Documentation/userspace-api/media/dvb/legacy_dvb_video.rst      | 2 +-
>  .../userspace-api/media/v4l/vidioc-subdev-g-routing.rst         | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/userspace-api/media/dvb/legacy_dvb_video.rst b/Documentation/userspace-api/media/dvb/legacy_dvb_video.rst
> index b9fd5cadae24..71d044605315 100644
> --- a/Documentation/userspace-api/media/dvb/legacy_dvb_video.rst
> +++ b/Documentation/userspace-api/media/dvb/legacy_dvb_video.rst
> @@ -344,7 +344,7 @@ Variables
>  
>      -  ..
>  
> -       -  :rspan:`5` ``stuct play``
> +       -  :rspan:`5` ``struct play``
>  
>         -  :rspan:`4` ``__s32 speed``
>  
> diff --git a/Documentation/userspace-api/media/v4l/vidioc-subdev-g-routing.rst b/Documentation/userspace-api/media/v4l/vidioc-subdev-g-routing.rst
> index 6f66ca38589e..164cf0ad3593 100644
> --- a/Documentation/userspace-api/media/v4l/vidioc-subdev-g-routing.rst
> +++ b/Documentation/userspace-api/media/v4l/vidioc-subdev-g-routing.rst
> @@ -67,7 +67,7 @@ subdevice routing table. This may be smaller or larger than the value of
>  drivers may adjust the requested routing table.
>  
>  The kernel can return a ``num_routes`` value larger than ``len_routes`` from
> -both ioctls. This indicates thare are more routes in the routing table than fits
> +both ioctls. This indicates there are more routes in the routing table than fits
>  the ``routes`` array. In this case, the ``routes`` array is filled by the kernel
>  with the first ``len_routes`` entries of the subdevice routing table. This is
>  not considered to be an error, and the ioctl call succeeds. If the applications

-- 
Regards,

Sakari Ailus