From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] some fixups for MediaTek cpufreq driver
Date: Mon, 17 Jul 2017 13:05:43 +0530 [thread overview]
Message-ID: <20170717073543.GL352@vireshk-i7> (raw)
In-Reply-To: <1500272192.16278.44.camel@mtkswgap22>
On 17-07-17, 14:16, Sean Wang wrote:
> Hi, Viresh
>
> I missed to add Acks from Rob for patch 2 and 3 since we sent out almost
> at the same time. Do I need to resend again for this or the series is
> okay for you?
Looks like you missed including Rafael for this series (He is the one
who applies these patches).
I will let him answer for this.
--
viresh
next prev parent reply other threads:[~2017-07-17 7:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 14:23 [PATCH v4 0/3] some fixups for MediaTek cpufreq driver sean.wang at mediatek.com
2017-07-10 14:23 ` [PATCH v4 1/3] cpufreq: mediatek: Add support of cpufreq to MT2701/MT7623 SoC sean.wang at mediatek.com
2017-07-11 2:49 ` Eddie Huang
2017-07-12 14:50 ` Matthias Brugger
2017-07-13 3:16 ` Viresh Kumar
2017-07-13 3:54 ` Eddie Huang
2017-07-17 8:05 ` Jean Delvare
2017-07-17 8:06 ` Jean Delvare
2017-07-10 14:23 ` [PATCH v4 2/3] dt-bindings: cpufreq: move MediaTek cpufreq dt-bindings document to proper place sean.wang at mediatek.com
2017-07-10 14:23 ` [PATCH v4 3/3] dt-bindings: cpufreq: enhance MediaTek cpufreq dt-binding document sean.wang at mediatek.com
2017-07-17 6:16 ` [PATCH v4 0/3] some fixups for MediaTek cpufreq driver Sean Wang
2017-07-17 7:35 ` Viresh Kumar [this message]
2017-07-17 11:33 ` Rafael J. Wysocki
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=20170717073543.GL352@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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