[PATCH v12 2/8] dt-bindings: media: platform: visconti: Add Toshiba Visconti Video Input Interface
Laurent Pinchart
laurent.pinchart at ideasonboard.com
Tue Dec 17 01:45:08 PST 2024
On Tue, Dec 17, 2024 at 06:43:22AM +0100, Krzysztof Kozlowski wrote:
> On 17/12/2024 01:00, yuji2.ishikawa at toshiba.co.jp wrote:
> > Hello Krzysztof
> >
> > Thank you for your review
> >
> >> -----Original Message-----
> >> From: Krzysztof Kozlowski <krzk at kernel.org>
> >> Sent: Monday, November 25, 2024 7:08 PM
> >> To: ishikawa yuji(石川 悠司 ○RDC□AITC○EA開)
> >> <yuji2.ishikawa at toshiba.co.jp>; Laurent Pinchart
> >> <laurent.pinchart at ideasonboard.com>; Mauro Carvalho Chehab
> >> <mchehab at kernel.org>; Rob Herring <robh at kernel.org>; Krzysztof Kozlowski
> >> <krzk+dt at kernel.org>; Conor Dooley <conor+dt at kernel.org>; Sakari Ailus
> >> <sakari.ailus at linux.intel.com>; Hans Verkuil <hverkuil-cisco at xs4all.nl>;
> >> iwamatsu nobuhiro(岩松 信洋 ○DITC□DIT○OST)
> >> <nobuhiro1.iwamatsu at toshiba.co.jp>
> >> Cc: linux-media at vger.kernel.org; linux-kernel at vger.kernel.org;
> >> linux-arm-kernel at lists.infradead.org; devicetree at vger.kernel.org
> >> Subject: Re: [PATCH v12 2/8] dt-bindings: media: platform: visconti: Add
> >> Toshiba Visconti Video Input Interface
> >>
> >> On 25/11/2024 10:21, Yuji Ishikawa wrote:
> >>> Adds the Device Tree binding documentation that allows to describe the
> >>> Video Input Interface found in Toshiba Visconti SoCs.
> >>>
> >>> Signed-off-by: Yuji Ishikawa <yuji2.ishikawa at toshiba.co.jp>
> >>> Reviewed-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu at toshiba.co.jp>
> >>
> >> Why this tag stayed and other was removed? What was the reason of tag
> >> removal?
> >>
> >
> > The stayed tag is due to internal review.
>
> Did the internal review really happened? How is it that immediately new
> version has internal review without any traces?
>
> I have doubts this review happened in the context of reviewer's
> statement of oversight.
>
> > The removed tag is due to code's change (split of csi2rx part) after the last review.
> > If the code is largely changed following the instruction of another reviewer
> > after obtaining the tags, how should the tags be handled?
>
> Drop all reviews and perform reviews on the list.
>
> Such internal review appearing afterwards is rather a proof it you are
> adding just the tags to satisfy your process. I have no way to even
> verify whether that person performed any reasonable review or maybe just
> acked your patch.
How do you verify that for public reviews ?
> I cannot even verify that that person understands the
> reviewer's statement of oversight.
>
>
> ...
>
> >>>
> >>> Changelog v11:
> >>> - no change
> >>>
> >>> Changelog v12:
> >>> - remove property "clock-noncontinuous" as VIIF switches both modes
> >>> automatically
> >>> - remove property "link-frequencies" as VIIF does not use the
> >>> information
> >>
> >> Driver does not use or hardware supports only one frequency?
> >
> > My comment was incorrect.
> > It should be "Driver does not use the information"
>
> Then this is not that helping. Maybe hardware supports only one frequency?
--
Regards,
Laurent Pinchart
More information about the linux-arm-kernel
mailing list