From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH v5 01/12] media: rcar-vin: Use correct count of remote subdevices
Date: Mon, 9 Jun 2025 09:41:21 +0000 [thread overview]
Message-ID: <aEasQagrdjSfvoNs@kekkonen.localdomain> (raw)
In-Reply-To: <aEar3NonNYosp4Nm@kekkonen.localdomain>
On Mon, Jun 09, 2025 at 09:39:40AM +0000, Sakari Ailus wrote:
> > * Changes since v4
> > - Use ARRAY_SIZE() instead of updating the incorrect define to
> > RVIN_REMOTES_MAX.
>
> Do you still need RVIN_REMOTES_MAX()? Couldn't you use ARRAY_SIZE()
> elsewhere, too?
I checked rcar-vin.h, please ignore the above comment.
--
Sakari Ailus
next prev parent reply other threads:[~2025-06-09 9:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 18:25 [PATCH v5 00/12] media: rcar-vin: Unify notifiers and enable MC on Gen2 Niklas Söderlund
2025-06-06 18:25 ` [PATCH v5 01/12] media: rcar-vin: Use correct count of remote subdevices Niklas Söderlund
2025-06-09 9:39 ` Sakari Ailus
2025-06-09 9:41 ` Sakari Ailus [this message]
2025-06-06 18:25 ` [PATCH v5 02/12] media: rcar-vin: Store platform info with group structure Niklas Söderlund
2025-06-12 0:19 ` Laurent Pinchart
2025-06-06 18:25 ` [PATCH v5 03/12] media: rcar-vin: Change link setup argument Niklas Söderlund
2025-06-12 0:31 ` Laurent Pinchart
2025-06-06 18:25 ` [PATCH v5 04/12] media: rcar-vin: Generate a VIN group ID for Gen2 Niklas Söderlund
2025-06-06 18:25 ` [PATCH v5 05/12] media: rcar-vin: Prepare for unifying all v4l-async notifiers Niklas Söderlund
2025-06-06 18:26 ` [PATCH v5 06/12] media: rcar-vin: Improve error paths for parallel devices Niklas Söderlund
2025-06-12 0:22 ` Laurent Pinchart
2025-06-06 18:26 ` [PATCH v5 07/12] media: rcar-vin: Merge all notifiers Niklas Söderlund
2025-06-12 23:15 ` Laurent Pinchart
2025-06-18 7:44 ` Geert Uytterhoeven
2025-06-18 8:58 ` Laurent Pinchart
2025-06-18 10:59 ` Geert Uytterhoeven
2025-06-18 11:03 ` Wolfram Sang
2025-06-06 18:26 ` [PATCH v5 08/12] media: rcar-vin: Always create a media pad Niklas Söderlund
2025-06-12 0:25 ` Laurent Pinchart
2025-06-06 18:26 ` [PATCH v5 09/12] media: rcar-vin: Remove NTSC workaround Niklas Söderlund
2025-06-12 23:17 ` Laurent Pinchart
2025-06-06 18:26 ` [PATCH v5 10/12] media: rcar-vin: Only expose VIN controls Niklas Söderlund
2025-06-12 23:28 ` Laurent Pinchart
2025-06-13 10:16 ` Niklas Söderlund
2025-06-06 18:26 ` [PATCH v5 11/12] media: rcar-vin: Enable media-graph on Gen2 Niklas Söderlund
2025-06-12 23:53 ` Laurent Pinchart
2025-06-13 9:38 ` Niklas Söderlund
2025-06-06 18:26 ` [PATCH v5 12/12] media: rcar-vin: Fold event notifier into only user Niklas Söderlund
2025-06-12 0:28 ` Laurent Pinchart
2025-06-12 7:22 ` Niklas Söderlund
2025-06-12 9:44 ` Laurent Pinchart
2025-06-12 9:56 ` Niklas Söderlund
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=aEasQagrdjSfvoNs@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=tomi.valkeinen+renesas@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox