[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c6dc5ed28c64f62b66e7b68b54c342b63e42d42.camel@mediatek.com>
Date: Mon, 11 Apr 2022 19:09:44 +0800
From: Rex-BC Chen <rex-bc.chen@...iatek.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: <rafael@...nel.org>, <robh+dt@...nel.org>, <krzk+dt@...nel.org>,
<matthias.bgg@...il.com>, <jia-wei.chang@...iatek.com>,
<roger.lu@...iatek.com>, <hsinyi@...gle.com>,
<linux-pm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
<Project_Global_Chrome_Upstream_Group@...iatek.com>
Subject: Re: [PATCH V2 15/15] cpufreq: mediatek: Use device print to show
logs
On Mon, 2022-04-11 at 08:59 +0530, Viresh Kumar wrote:
> On 08-04-22, 12:59, Rex-BC Chen wrote:
> > Replace pr_* with dev_* to show logs.
> >
> > Signed-off-by: Rex-BC Chen <rex-bc.chen@...iatek.com>
> > ---
> > drivers/cpufreq/mediatek-cpufreq.c | 41 +++++++++++++++++---------
> > ----
> > 1 file changed, 23 insertions(+), 18 deletions(-)
>
> One should always arrange the patches in this form:
>
> - Fix bugs first (since they need to be applied first and need to go
> to stable kernels too).
>
> - Trivial fixes next, like this one which you chose to be present at
> 15/15. I would have applied this one right away, if it wasn't he
> last one, because of which we have conflicts now.
>
> - Non-trivial patches later, so reviews on them don't affect other
> patches.
>
Hello Viresh,
Thanks for your review and suggestions.
I will put this patch to first in next version.
BRs,
Rex
Powered by blists - more mailing lists