From: "Måns Rullgård" <mans@mansr.com>
To: Mason <mpeg.blue@free.fr>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux PM <linux-pm@vger.kernel.org>,
cpufreq <cpufreq@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: RFC on cpufreq implementation
Date: Wed, 04 Feb 2015 00:32:40 +0000 [thread overview]
Message-ID: <yw1xlhkea53r.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <54D162B6.2050602@free.fr> (Mason's message of "Tue, 03 Feb 2015 16:07:18 -0800")
Mason <mpeg.blue@free.fr> writes:
> Are you saying that use of DeviceTree is mandatory for new ARM ports?
Yes.
--
Måns Rullgård
mans@mansr.com
WARNING: multiple messages have this Message-ID (diff)
From: mans@mansr.com (Måns Rullgård)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC on cpufreq implementation
Date: Wed, 04 Feb 2015 00:32:40 +0000 [thread overview]
Message-ID: <yw1xlhkea53r.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <54D162B6.2050602@free.fr> (Mason's message of "Tue, 03 Feb 2015 16:07:18 -0800")
Mason <mpeg.blue@free.fr> writes:
> Are you saying that use of DeviceTree is mandatory for new ARM ports?
Yes.
--
M?ns Rullg?rd
mans at mansr.com
next prev parent reply other threads:[~2015-02-04 0:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 17:24 RFC on cpufreq implementation Mason
2015-01-15 17:24 ` Mason
2015-01-16 9:08 ` Krzysztof Kozlowski
2015-01-16 9:08 ` Krzysztof Kozlowski
2015-01-16 11:10 ` Mason
2015-01-16 11:10 ` Mason
2015-01-16 11:43 ` Krzysztof Kozlowski
2015-01-16 11:43 ` Krzysztof Kozlowski
2015-01-16 11:43 ` Krzysztof Kozlowski
2015-01-16 12:10 ` Javi Merino
2015-01-16 12:10 ` Javi Merino
2015-01-16 14:00 ` Mason
2015-01-16 14:00 ` Mason
2015-01-19 7:52 ` Viresh Kumar
2015-01-19 7:52 ` Viresh Kumar
2015-01-19 22:03 ` Mason
2015-01-19 22:03 ` Mason
2015-01-20 3:55 ` Viresh Kumar
2015-01-20 3:55 ` Viresh Kumar
2015-01-19 9:22 ` Amit Kucheria
2015-01-19 9:22 ` Amit Kucheria
2015-01-19 22:13 ` Mason
2015-01-19 22:13 ` Mason
2015-01-29 16:43 ` Mason
2015-01-29 16:43 ` Mason
2015-01-30 1:15 ` Viresh Kumar
2015-01-30 1:15 ` Viresh Kumar
2015-01-30 23:44 ` Mason
2015-01-30 23:44 ` Mason
2015-02-02 3:58 ` Viresh Kumar
2015-02-02 3:58 ` Viresh Kumar
2015-02-04 0:07 ` Mason
2015-02-04 0:07 ` Mason
2015-02-04 0:32 ` Måns Rullgård [this message]
2015-02-04 0:32 ` Måns Rullgård
2015-02-04 4:12 ` Viresh Kumar
2015-02-04 4:12 ` Viresh Kumar
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=yw1xlhkea53r.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=arnd@arndb.de \
--cc=cpufreq@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mpeg.blue@free.fr \
--cc=rjw@rjwysocki.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.