Linux Power Management development
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael J Wysocki <rjw@rjwysocki.net>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 RESEND] cpufreq: pxa: convert to clock API
Date: Thu, 11 Jan 2018 18:26:18 +0100	[thread overview]
Message-ID: <87inc8b939.fsf@belgarion.home> (raw)
In-Reply-To: <20180111083519.GG3626@vireshk-i7> (Viresh Kumar's message of "Thu, 11 Jan 2018 14:05:19 +0530")

Viresh Kumar <viresh.kumar@linaro.org> writes:

> On 11-01-18, 09:10, Robert Jarzmik wrote:
>> Robert Jarzmik <robert.jarzmik@free.fr> writes:
>> 
>> > As the clock settings have been introduced into the clock pxa drivers,
>> > which are now available to change the CPU clock by themselves, remove
>> > the clock handling from this driver, and rely on pxa clock drivers.
>> >
>> > Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
>> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>> > ---
>> > This is a resend of a formerly acked patch as all dependencies have
>> > hit upstream, see :
>> > 	https://www.spinics.net/lists/arm-kernel/msg540181.html
>> > ---
>> >  drivers/cpufreq/pxa2xx-cpufreq.c | 191 ++++++++-------------------------------
>> >  1 file changed, 39 insertions(+), 152 deletions(-)
>> 
>> Hi Rafael,
>> 
>> Would you consider taking this patch in ? It was submitted and acked a long ago,
>> and as the above mail says, the dependencies have hit mainline for quite some
>> time now.
>
> Check linux-next.
>
> d9278077385f cpufreq: pxa: convert to clock API
Thanks and sorry for the noise.

Cheers.

-- 
Robert

      reply	other threads:[~2018-01-11 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-14 21:51 [PATCH v3 RESEND] cpufreq: pxa: convert to clock API Robert Jarzmik
2018-01-11  8:10 ` Robert Jarzmik
2018-01-11  8:35   ` Viresh Kumar
2018-01-11 17:26     ` Robert Jarzmik [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=87inc8b939.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox