From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PM / OPP: Remove ARCH_HAS_OPP
Date: Fri, 6 Jun 2014 14:08:50 +0100 [thread overview]
Message-ID: <20140606130850.GO2520@sirena.org.uk> (raw)
In-Reply-To: <20140606125003.GA13332@verge.net.au>
On Fri, Jun 06, 2014 at 09:50:06PM +0900, Simon Horman wrote:
> On Fri, Jun 06, 2014 at 09:14:01PM +0900, Magnus Damm wrote:
> > I'm not sure about the expected merge order for this kind of change vs
> > queued up stuff in the renesas git tree, but I believe the following
> > patch selects ARCH_HAS_OPP:
> > [PATCH v3] ARM: shmobile: Mark all SoCs in shmobile as CPUFreq, capable
> I propose that we fix that up by adding an incremental patch to
> mach-shmobile via my renesas tree once the dependency (assuming there is
> one) is in Linus's tree.
Yes, the conversion to make ARCH_HAS_OPP unused is in Raphael's tree for
the merge window. I'd expect this patch to end up going after the merge
window (or at the end I guess).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140606/e1c776b1/attachment.sig>
next prev parent reply other threads:[~2014-06-06 13:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 10:36 [PATCH] PM / OPP: Remove ARCH_HAS_OPP Mark Brown
2014-06-06 11:14 ` Simon Horman
2014-06-06 12:14 ` Magnus Damm
2014-06-06 12:50 ` Simon Horman
2014-06-06 13:01 ` Magnus Damm
2014-06-06 13:08 ` Mark Brown [this message]
2014-06-06 21:15 ` Rafael J. Wysocki
2014-06-09 19:49 ` Mark Brown
2014-06-09 22:22 ` Rafael J. Wysocki
2014-06-09 22:51 ` Mark Brown
2014-06-10 0:15 ` Rafael J. Wysocki
2014-06-06 13:45 ` Rob Herring
2014-06-06 14:33 ` Nishanth Menon
2014-06-09 1:56 ` Shawn Guo
2014-06-09 4:49 ` Viresh Kumar
2014-07-22 14:43 Mark Brown
2014-07-22 23:51 ` Rafael J. Wysocki
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=20140606130850.GO2520@sirena.org.uk \
--to=broonie@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).