From: Stephen Boyd <sboyd@kernel.org>
To: Sricharan R <sricharan@codeaurora.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
robh@kernel.org, linux-pm@vger.kernel.org, rjw@rjwysocki.net,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
david.brown@linaro.org, robh+dt@kernel.org,
linux-arm-msm@vger.kernel.org, andy.gross@linaro.org,
linux-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 14/15] cpufreq: Add module to register cpufreq on Krait CPUs
Date: Wed, 14 Mar 2018 09:45:44 -0700 [thread overview]
Message-ID: <152104594491.179530.16525167791258003396@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <ab5ad9c2-2016-47ca-b748-833ff6e75f70@codeaurora.org>
Quoting Sricharan R (2018-02-26 02:15:59)
> Hi Viresh,
>
> On 2/26/2018 3:34 PM, Viresh Kumar wrote:
> > On 26-02-18, 15:23, Sricharan R wrote:
> >> From: Stephen Boyd <sboyd@codeaurora.org>
> >
> > Is this email id still valid ?
> >
>
> Yes. codeaurora id should exist.
>
Yes it exists and I am checking it.
next prev parent reply other threads:[~2018-03-14 16:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 9:53 [PATCH v7 00/15] Krait clocks + Krait CPUfreq Sricharan R
2018-02-26 9:53 ` [PATCH v7 01/15] ARM: Add Krait L2 register accessor functions Sricharan R
2018-02-26 9:53 ` [PATCH v7 02/15] clk: mux: Split out register accessors for reuse Sricharan R
2018-02-26 9:53 ` [PATCH v7 03/15] clk: qcom: Add support for High-Frequency PLLs (HFPLLs) Sricharan R
2018-02-26 9:53 ` [PATCH v7 04/15] clk: qcom: Add HFPLL driver Sricharan R
2018-02-26 9:53 ` [PATCH v7 05/15] dt-bindings: clock: Document qcom,hfpll Sricharan R
2018-02-26 9:53 ` [PATCH v7 06/15] clk: qcom: Add MSM8960/APQ8064's HFPLLs Sricharan R
2018-02-26 9:53 ` [PATCH v7 07/15] clk: qcom: Add IPQ806X's HFPLLs Sricharan R
2018-02-26 9:53 ` [PATCH v7 08/15] clk: qcom: Add support for Krait clocks Sricharan R
2018-02-26 9:53 ` [PATCH v7 09/15] clk: qcom: Add KPSS ACC/GCC driver Sricharan R
2018-02-26 9:53 ` [PATCH v7 10/15] dt-bindings: arm: Document qcom,kpss-gcc Sricharan R
2018-02-26 9:53 ` [PATCH v7 11/15] clk: qcom: Add Krait clock controller driver Sricharan R
2018-02-26 9:53 ` [PATCH v7 12/15] dt-bindings: clock: Document qcom,krait-cc Sricharan R
2018-02-26 9:53 ` [PATCH v7 13/15] clk: qcom: Add safe switch hook for krait mux clocks Sricharan R
2018-02-26 9:53 ` [PATCH v7 14/15] cpufreq: Add module to register cpufreq on Krait CPUs Sricharan R
2018-02-26 10:04 ` Viresh Kumar
2018-02-26 10:15 ` Sricharan R
2018-03-14 16:45 ` Stephen Boyd [this message]
2018-02-26 9:53 ` [PATCH v7 15/15] dt-bindings: cpufreq: Document operating-points-v2-krait-cpu Sricharan R
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=152104594491.179530.16525167791258003396@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sricharan@codeaurora.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).