[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5464b036-1b90-e7e5-0bb9-100a1fc96a8e@linaro.org>
Date: Mon, 28 Aug 2023 20:31:34 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: rfoss@...nel.org, todor.too@...il.com, agross@...nel.org,
andersson@...nel.org, konrad.dybcio@...aro.org, mchehab@...nel.org,
hverkuil-cisco@...all.nl, sakari.ailus@...ux.intel.com,
andrey.konovalov@...aro.org, linux-media@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 05/15] media: qcom: camss: Pass line_num from compat
resources
On 28/08/2023 19:36, Laurent Pinchart wrote:
> Should the variable then be renamed to num_rdi or similar ?
Yes but, the use of "line num" is pretty extensive. I plan a series to
normalise the namespace a bit later on. I'm just trying to scope limit
the extent of the changes in one blob.
- rdi_num
- size of struct resource strings
being two that are "high up" on my TODOs.
---
bod
Powered by blists - more mailing lists