All of lore.kernel.org
 help / color / mirror / Atom feed
From: Umang Jain <umang.jain@ideasonboard.com>
To: linux-media@vger.kernel.org
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Umang Jain <umang.jain@ideasonboard.com>
Subject: [PATCH] media: Documentation: dev-subdev: Fix sentence conjunction
Date: Fri, 12 Apr 2024 14:58:36 +0530	[thread overview]
Message-ID: <20240412092836.69031-1-umang.jain@ideasonboard.com> (raw)

Fix sentence conjunction in the streams and routes section.

Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
---
 Documentation/userspace-api/media/v4l/dev-subdev.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/userspace-api/media/v4l/dev-subdev.rst b/Documentation/userspace-api/media/v4l/dev-subdev.rst
index 43988516acdd..7f6620cbdf78 100644
--- a/Documentation/userspace-api/media/v4l/dev-subdev.rst
+++ b/Documentation/userspace-api/media/v4l/dev-subdev.rst
@@ -561,7 +561,7 @@ selections. The order of configuring formats and selections along a stream is
 the same as without streams (see :ref:`format-propagation`).
 
 Instead of the sub-device wide merging of streams from all sink pads
-towards all source pads, data flows for each route are separate from each
+towards all source pads, data flows for each route that are separate from each
 other. Any number of routes from streams on sink pads towards streams on
 source pads is allowed, to the extent supported by drivers. For every
 stream on a source pad, however, only a single route is allowed.
-- 
2.44.0


             reply	other threads:[~2024-04-12  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12  9:28 Umang Jain [this message]
2024-04-12  9:46 ` [PATCH] media: Documentation: dev-subdev: Fix sentence conjunction Kieran Bingham

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=20240412092836.69031-1-umang.jain@ideasonboard.com \
    --to=umang.jain@ideasonboard.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=tomi.valkeinen@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.