[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <12bfcd12-28ef-4fa9-9a46-f370bdb4cce8@linaro.org>
Date: Mon, 13 May 2024 18:43:17 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: "Gjorgji Rosikopulos (Consultant)" <quic_grosikop@...cinc.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>, rfoss@...nel.org,
todor.too@...il.com, andersson@...nel.org, konrad.dybcio@...aro.org,
mchehab@...nel.org
Cc: linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, laurent.pinchart@...asonboard.com,
hverkuil-cisco@...all.nl, quic_hariramp@...cinc.com
Subject: Re: [PATCH v3 5/8] media: qcom: camss: Move format related functions
On 13/05/2024 17:52, Gjorgji Rosikopulos (Consultant) wrote:
>> 0 as an error condition indicator is not very common, at least it shall be
>> documented in the comment.
> The original function was vfe_find_code. This change moves all format
> related functions across the sub-device files to camss-format
> I believe that 0 is default format
For this series changing the result code is extraneous, agree.
We can debate such a change in a standalone patch on its own merits.
---
bod
Powered by blists - more mailing lists