From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH 1/1] cpufreq: exynos: Disable on multiplatform build
Date: Tue, 08 Apr 2014 14:13:57 +0200 [thread overview]
Message-ID: <2111902.UpDYE9Wpx2@vostro.rjw.lan> (raw)
In-Reply-To: <CAK9yfHxq7P1ngF9c-3P=HefoLrn3oZ9UngRc9DT_6g-xC0OtQg@mail.gmail.com>
On Thursday, April 03, 2014 05:13:58 PM Sachin Kamat wrote:
> On 2 April 2014 16:35, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > On 2 April 2014 16:33, Sachin Kamat <sachin.kamat@linaro.org> wrote:
> >> The current exynos cpufreq drivers are not multiplatform compliant
> >> and give build errors as they refer to header files from machine
> >> directory. Work to migrate them to generic cpufreq framework is under
> >> progress. Till such time disable the build on multiplatform so that
> >> other multiplatform ready features get tested.
> >>
> >> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> >> Cc: Arnd Bergmann <arnd@arndb.de>
>
> >
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Rafael,
> Please queue this patch for your upcoming pull request to Linus.
I will, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2014-04-08 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 11:03 [PATCH 1/1] cpufreq: exynos: Disable on multiplatform build Sachin Kamat
2014-04-02 11:05 ` Viresh Kumar
2014-04-03 11:43 ` Sachin Kamat
2014-04-08 12:13 ` Rafael J. Wysocki [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=2111902.UpDYE9Wpx2@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=arnd@arndb.de \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sachin.kamat@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).