From: Hector Yuan <hector.yuan@mediatek.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: <linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Rob Herring" <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Vinod Koul <vkoul@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Anson Huang <Anson.Huang@nxp.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"Olof Johansson" <olof@lixom.net>, <wsd_upstream@mediatek.com>
Subject: Re: [PATCH v3] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver
Date: Tue, 8 Sep 2020 13:52:24 +0800 [thread overview]
Message-ID: <1599544344.17800.2.camel@mtkswgap22> (raw)
In-Reply-To: <20200908051416.na567g3mr7zbyr6h@vireshk-i7>
On Tue, 2020-09-08 at 10:44 +0530, Viresh Kumar wrote:
> On 08-09-20, 10:35, Hector Yuan wrote:
> > Hi, Sirs:
> >
> > Please kindly let me know your review thoughts of this patch.
> > Appreciated.
>
> Please don't send new patchsets in hurry, it isn't going to help any
> of us. V3 doesn't address all the review comments you received in V2
> and so there is no point reviewing it.
>
> Please send a new version which addresses all the comments you got.
>
OK, I will send V4 which addresses all the comments.
prev parent reply other threads:[~2020-09-08 5:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 13:01 [PATCH v3] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Hector Yuan
2020-08-26 13:01 ` [PATCH v3 1/2] " Hector Yuan
2020-08-26 13:01 ` [PATCH v3 2/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW Hector Yuan
2020-09-08 2:35 ` [PATCH v3] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Hector Yuan
2020-09-08 5:14 ` Viresh Kumar
2020-09-08 5:52 ` Hector Yuan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1599544344.17800.2.camel@mtkswgap22 \
--to=hector.yuan@mediatek.com \
--cc=Anson.Huang@nxp.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
--cc=wsd_upstream@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).