[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z4DV8zVqQf9Bl0X5@kekkonen.localdomain>
Date: Fri, 10 Jan 2025 08:10:27 +0000
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Alain Volmat <alain.volmat@...s.st.com>
Cc: Hugues Fruchet <hugues.fruchet@...s.st.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Hans Verkuil <hverkuil@...all.nl>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-media@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v2 0/8] media: stm32: csi / dcmipp corrections
On Fri, Jan 10, 2025 at 08:08:47AM +0000, Sakari Ailus wrote:
> Hi Alain,
>
> On Wed, Jan 08, 2025 at 02:16:03PM +0100, Alain Volmat wrote:
> > Various fixes within the stm32 csi bindings/drivers and
> > stm32 dcmipp driver.
> >
> > Signed-off-by: Alain Volmat <alain.volmat@...s.st.com>
>
> Thanks for the update. I tried to apply this but it doesn't, and the
> culprit appears to be this line in dcmipp_graph_notify_bound():
>
> unsigned int ret;
>
> That appears to be a bug as such. The interesting thing is that the patch
> changing things around it presumes
>
> int ret;
>
> so it won't apply. Do you already have a patch that fixes it? It should be
> cc'd to stable, too, with a Fixes: tag.
Ok, the tag isn't necessary as there lack of the sign doesn't seem to
matter in this case.
--
Sakari Ailus
Powered by blists - more mailing lists