From: Sudeep Holla <sudeep.holla@arm.com>
To: Ilia Lin <ilialin@codeaurora.org>
Cc: vireshk@kernel.org, nm@ti.com, sboyd@kernel.org, robh@kernel.org,
mark.rutland@arm.com, rjw@rjwysocki.net,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v11 0/2] Kryo CPU scaling driver
Date: Wed, 23 May 2018 16:41:25 +0100 [thread overview]
Message-ID: <20180523154125.GA30427@e107155-lin> (raw)
In-Reply-To: <f53d6035-d409-4535-9dd0-03baedc9b4a8@email.android.com>
On Wed, May 23, 2018 at 06:34:06PM +0300, Ilia Lin wrote:
> It may be merged alone safely. However to actually work, it needs a clock
> driver as well, and the OPP tables in tue device tree. Those are submitted now
> 8n 2 separate series. This is in order to provide each maintainer with domain
> specific series, as per Viresh's suggestion.
I understand that. I was trying to get overall structure to better understand
how it all glue together in the system(just for self education).
--
Regards,
Sudeep
prev parent reply other threads:[~2018-05-23 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 12:38 [PATCH v11 0/2] Kryo CPU scaling driver Ilia Lin
2018-05-23 12:38 ` [PATCH v11 1/2] cpufreq: Add " Ilia Lin
2018-05-23 13:25 ` Sudeep Holla
2018-05-23 17:42 ` ilialin
2018-05-24 4:34 ` Viresh Kumar
2018-05-24 9:37 ` Sudeep Holla
2018-05-24 4:37 ` Viresh Kumar
2018-05-23 12:38 ` [PATCH v11 2/2] dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu Ilia Lin
2018-05-23 13:54 ` [PATCH v11 0/2] Kryo CPU scaling driver Sudeep Holla
2018-05-23 15:34 ` Ilia Lin
2018-05-23 15:41 ` Sudeep Holla [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=20180523154125.GA30427@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=ilialin@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sboyd@kernel.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;
as well as URLs for NNTP newsgroup(s).