From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PM / OPP: Remove ARCH_HAS_OPP
Date: Fri, 06 Jun 2014 20:57:51 +0000 [thread overview]
Message-ID: <3122018.iBNBjMKNbN@vostro.rjw.lan> (raw)
In-Reply-To: <20140606130850.GO2520@sirena.org.uk>
On Friday, June 06, 2014 02:08:50 PM Mark Brown wrote:
>
> --cU9XODsizZBnwgll
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> 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.
Perhaps already merged?
Rafael
WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Kukjin Kim <kgene.kim@samsung.com>,
Russell King <linux@arm.linux.org.uk>,
Linux PM list <linux-pm@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
SH-Linux <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Michal Simek <michal.simek@xilinx.com>,
linux-samsung-soc@vger.kernel.org,
Simon Horman <horms@verge.net.au>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Sascha Hauer <kernel@pengutronix.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Shawn Guo <shawn.guo@freescale.com>
Subject: Re: [PATCH] PM / OPP: Remove ARCH_HAS_OPP
Date: Fri, 06 Jun 2014 23:15:06 +0200 [thread overview]
Message-ID: <3122018.iBNBjMKNbN@vostro.rjw.lan> (raw)
In-Reply-To: <20140606130850.GO2520@sirena.org.uk>
On Friday, June 06, 2014 02:08:50 PM Mark Brown wrote:
>
> --cU9XODsizZBnwgll
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> 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.
Perhaps already merged?
Rafael
WARNING: multiple messages have this Message-ID (diff)
From: rjw@rjwysocki.net (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PM / OPP: Remove ARCH_HAS_OPP
Date: Fri, 06 Jun 2014 23:15:06 +0200 [thread overview]
Message-ID: <3122018.iBNBjMKNbN@vostro.rjw.lan> (raw)
In-Reply-To: <20140606130850.GO2520@sirena.org.uk>
On Friday, June 06, 2014 02:08:50 PM Mark Brown wrote:
>
> --cU9XODsizZBnwgll
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> 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.
Perhaps already merged?
Rafael
next prev parent reply other threads:[~2014-06-06 20:57 UTC|newest]
Thread overview: 49+ 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 10:36 ` Mark Brown
2014-06-06 10:36 ` Mark Brown
2014-06-06 11:14 ` Simon Horman
2014-06-06 11:14 ` Simon Horman
2014-06-06 11:14 ` Simon Horman
2014-06-06 12:14 ` Magnus Damm
2014-06-06 12:14 ` Magnus Damm
2014-06-06 12:14 ` Magnus Damm
2014-06-06 12:50 ` Simon Horman
2014-06-06 12:50 ` Simon Horman
2014-06-06 12:50 ` Simon Horman
2014-06-06 13:01 ` Magnus Damm
2014-06-06 13:01 ` Magnus Damm
2014-06-06 13:01 ` Magnus Damm
2014-06-06 13:08 ` Mark Brown
2014-06-06 13:08 ` Mark Brown
2014-06-06 13:08 ` Mark Brown
2014-06-06 20:57 ` Rafael J. Wysocki [this message]
2014-06-06 21:15 ` Rafael J. Wysocki
2014-06-06 21:15 ` Rafael J. Wysocki
2014-06-09 19:49 ` Mark Brown
2014-06-09 19:49 ` Mark Brown
2014-06-09 19:49 ` Mark Brown
2014-06-09 22:22 ` Rafael J. Wysocki
2014-06-09 22:22 ` Rafael J. Wysocki
2014-06-09 22:22 ` Rafael J. Wysocki
2014-06-09 22:51 ` Mark Brown
2014-06-09 22:51 ` Mark Brown
2014-06-09 22:51 ` Mark Brown
2014-06-09 23:57 ` Rafael J. Wysocki
2014-06-10 0:15 ` Rafael J. Wysocki
2014-06-10 0:15 ` Rafael J. Wysocki
2014-06-06 13:45 ` Rob Herring
2014-06-06 13:45 ` Rob Herring
2014-06-06 13:45 ` Rob Herring
2014-06-06 14:33 ` Nishanth Menon
2014-06-06 14:33 ` Nishanth Menon
2014-06-06 14:33 ` Nishanth Menon
2014-06-09 1:56 ` Shawn Guo
2014-06-09 1:56 ` Shawn Guo
2014-06-09 1:56 ` Shawn Guo
2014-06-09 4:49 ` Viresh Kumar
2014-06-09 4:49 ` Viresh Kumar
2014-06-09 4:49 ` Viresh Kumar
2014-07-22 14:43 Mark Brown
2014-07-22 14:43 ` Mark Brown
2014-07-22 23:51 ` Rafael J. Wysocki
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=3122018.iBNBjMKNbN@vostro.rjw.lan \
--to=rjw@rjwysocki.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 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.