public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: mvebu: ARCH_HAS_CPUFREQ
Date: Thu, 17 Jul 2014 07:41:00 -0400	[thread overview]
Message-ID: <20140717114100.GE13108@titan.lakedaemon.net> (raw)
In-Reply-To: <20140717113245.121277bb@free-electrons.com>

On Thu, Jul 17, 2014 at 11:32:45AM +0200, Thomas Petazzoni wrote:
> Dear Paul Bolle,
> 
> On Thu, 17 Jul 2014 11:18:22 +0200, Paul Bolle wrote:
> 
> > 0) Linux-next includes your commit a02829b0485e ("ARM: mvebu: allow
> > enabling of cpufreq on Armada XP") as of today (next-20140717).
> > 
> > 1) That commit only adds
> >     select ARCH_HAS_CPUFREQ
> > 
> > to a Kconfig entry. But ARCH_HAS_CPUFREQ was dropped in v3.16-rc2, see
> > commit 19682f72f5db ("ARM: Remove ARCH_HAS_CPUFREQ config option").
> > While I don't know what you want to achieve here, selecting
> > ARCH_HAS_CPUFREQ certainly won't help you.
> 
> Thanks for the notification. The issue is that the cpufreq branch I've
> sent to Jason is based on 3.16-rc1, which does not have 19682f72f5db.
> 
> Jason, I believe you could simply drop the patch a02829b0485e, since
> all it does is selecting this ARCH_HAS_CPUFREQ option which no longer
> exists.

Dropped from mvebu/soc-cpufreq.  mvebu/for-next is updated and build
testing.  It'll be pushed out in a bit.

Thanks for the heads up Paul!

thx,

Jason.

  reply	other threads:[~2014-07-17 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  9:18 ARM: mvebu: ARCH_HAS_CPUFREQ Paul Bolle
2014-07-17  9:32 ` Thomas Petazzoni
2014-07-17 11:41   ` Jason Cooper [this message]
2014-07-17 17:19     ` mat

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=20140717114100.GE13108@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.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