[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180605105716.GT16230@vkoul-mobl>
Date: Tue, 5 Jun 2018 16:27:16 +0530
From: Vinod <vkoul@...nel.org>
To: Stanimir Varbanov <stanimir.varbanov@...aro.org>
Cc: Vikash Garodia <vgarodia@...eaurora.org>, hverkuil@...all.nl,
mchehab@...nel.org, robh@...nel.org, mark.rutland@....com,
andy.gross@...aro.org, bjorn.andersson@...aro.org,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-soc@...r.kernel.org,
devicetree@...r.kernel.org, acourbot@...omium.org
Subject: Re: [PATCH v2 1/5] media: venus: add a routine to reset ARM9
On 02-06-18, 01:15, Stanimir Varbanov wrote:
> Hi Vikash,
>
> On 1.06.2018 23:26, Vikash Garodia wrote:
> > Add a new routine to reset the ARM9 and brings it
> > out of reset. This is in preparation to add PIL
> > functionality in venus driver.
>
> please squash this patch with 4/5. I don't see a reason to add a function
> which is not used. Shouldn't this produce gcc warnings?
Yes this would but in a multi patch series that is okay as subsequent
patches would use that and end result in no warning.
Splitting logically is good and typical practice in kernel to add the
routine followed by usages..
--
~Vinod
Powered by blists - more mailing lists