[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160109230330.GG576@valkosipuli.retiisi.org.uk>
Date: Sun, 10 Jan 2016 01:03:30 +0200
From: Sakari Ailus <sakari.ailus@....fi>
To: Javier Martinez Canillas <javier@....samsung.com>
Cc: linux-kernel@...r.kernel.org, Nikhil Devshatwar <nikhil.nd@...com>,
Kukjin Kim <kgene@...nel.org>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Andrzej Hajda <a.hajda@...sung.com>,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Guennadi Liakhovetski <g.liakhovetski@....de>,
linux-samsung-soc@...r.kernel.org,
Kyungmin Park <kyungmin.park@...sung.com>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
"Prabhakar\"" <prabhakar.csengg@...il.com>,
Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Hans Verkuil <hans.verkuil@...co.com>,
linux-arm-kernel@...ts.infradead.org, linux-media@...r.kernel.org
Subject: Re: [PATCH 0/8] [media] Check v4l2_of_parse_endpoint() ret val in
all drivers
Hi Javier,
On Thu, Jan 07, 2016 at 03:27:14PM -0300, Javier Martinez Canillas wrote:
> Hello,
>
> When discussing a patch [0] with Laurent Pinchart for another series I
> mentioned to him that most callers of v4l2_of_parse_endpoint() weren't
> checking the return value. This is likely due the function kernel-doc
> stating incorrectly that the return value is always 0 but can return a
> negative error code on failure.
>
> This trivial patch series fixes the function kernel-doc and add proper
> error checking in all the drivers that are currently not doing so.
After fixing patches 5 and 6,
Acked-by: Sakari Ailus <sakari.ailus@...ux.intel.com>
--
Kind regards,
Sakari Ailus
e-mail: sakari.ailus@....fi XMPP: sailus@...iisi.org.uk
Powered by blists - more mailing lists