From: Ilia Lin <ilialin@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v14 0/2] Kryo CPU scaling driver
Date: Wed, 30 May 2018 14:06:27 +0300 [thread overview]
Message-ID: <A7737343-1D4B-490C-9E08-DA1DBB25D5B8@codeaurora.org> (raw)
In-Reply-To: <20180530091535.bzvhg4bvn32mqwgq@vireshk-i7>
Just like Viresh said, this is fixed in the v15.
On May 30, 2018 12:15:35 PM GMT+03:00, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>On 30-05-18, 10:08, Rafael J. Wysocki wrote:
>> On Fri, May 25, 2018 at 2:07 PM, Ilia Lin <ilialin@codeaurora.org>
>wrote:
>> > [v14]
>> > * Addressed comment from Sudeep about DT compatible
>> > * Added MAINTAINERS entry
>>
>> This causes a build issue to occur in my bleeding-edge branch.
>>
>> Does it depend on anything new in arm-soc?
>
>He already sent a v15 and the changelog suggest he fixed that build
>issue.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2018-05-30 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 12:07 Ilia Lin
2018-05-25 12:07 ` [PATCH v14 1/2] cpufreq: Add " Ilia Lin
2018-05-25 12:07 ` [PATCH v14 2/2] dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu Ilia Lin
2018-05-29 11:11 ` [PATCH v14 0/2] Kryo CPU scaling driver Amit Kucheria
2018-05-30 8:08 ` Rafael J. Wysocki
2018-05-30 9:15 ` Viresh Kumar
2018-05-30 11:06 ` Ilia Lin [this message]
2018-05-25 12:41 Ilia Lin
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=A7737343-1D4B-490C-9E08-DA1DBB25D5B8@codeaurora.org \
--to=ilialin@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.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
all inboxes | Powered by JetHome®