From: shaikh kamaluddin <shaikhkamal2012@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: media: fix spelling errors
Date: Tue, 28 Jul 2026 22:23:08 +0530 [thread overview]
Message-ID: <amjedHeBeC-eNINK@acer-nitro-anv15-41> (raw)
In-Reply-To: <amivy2PF7EXVXglr@kekkonen.localdomain>
On Tue, Jul 28, 2026 at 04:34:03PM +0300, Sakari Ailus wrote:
> 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@gmail.com>
>
> 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
Thanks for the review — sent v2 [1] with the Documentation: prefix and my
full name in From/Signed-off-by:
[1] https://lore.kernel.org/all/20260728145252.9326-1-shaikhkamal2012@gmail.com/
Shaikh Kamaluddin
prev parent reply other threads:[~2026-07-28 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 6:54 shaikh.kamal
2026-07-28 13:34 ` Sakari Ailus
2026-07-28 16:53 ` shaikh kamaluddin [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=amjedHeBeC-eNINK@acer-nitro-anv15-41 \
--to=shaikhkamal2012@gmail.com \
--cc=hverkuil+cisco@kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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
all inboxes | Powered by JetHome®