From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PM / OPP: Remove ARCH_HAS_OPP
Date: Mon, 09 Jun 2014 23:57:55 +0000 [thread overview]
Message-ID: <1857766.e38RV3V2OT@vostro.rjw.lan> (raw)
In-Reply-To: <20140609225142.GA5099@sirena.org.uk>
On Monday, June 09, 2014 11:51:42 PM Mark Brown wrote:
>
> --fYgRtaZIy+F1uhp1
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> On Tue, Jun 10, 2014 at 12:22:07AM +0200, Rafael J. Wysocki wrote:
> > On Monday, June 09, 2014 08:49:17 PM Mark Brown wrote:
>
> > > Yes, looks like it is.
>
> > But it doesn't apply for me on top of the current Linus' tree.
>
> > Can you please rebase?
>
> It probably depends on other people's trees too, I just killed all the
> usages in -next - I gather the SH trees added some new ones for example.
> I'd expect it'll apply after the merge window, if not that's the time to
> look at it.
OK
WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mark Brown <broonie@kernel.org>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Kukjin Kim <kgene.kim@samsung.com>, Rob Herring <robh@kernel.org>,
Shawn Guo <shawn.guo@freescale.com>,
Sascha Hauer <kernel@pengutronix.de>,
Tony Lindgren <tony@atomide.com>,
Michal Simek <michal.simek@xilinx.com>,
Linux PM list <linux-pm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-samsung-soc@vger.kernel.org,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
SH-Linux <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] PM / OPP: Remove ARCH_HAS_OPP
Date: Tue, 10 Jun 2014 02:15:16 +0200 [thread overview]
Message-ID: <1857766.e38RV3V2OT@vostro.rjw.lan> (raw)
In-Reply-To: <20140609225142.GA5099@sirena.org.uk>
On Monday, June 09, 2014 11:51:42 PM Mark Brown wrote:
>
> --fYgRtaZIy+F1uhp1
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> On Tue, Jun 10, 2014 at 12:22:07AM +0200, Rafael J. Wysocki wrote:
> > On Monday, June 09, 2014 08:49:17 PM Mark Brown wrote:
>
> > > Yes, looks like it is.
>
> > But it doesn't apply for me on top of the current Linus' tree.
>
> > Can you please rebase?
>
> It probably depends on other people's trees too, I just killed all the
> usages in -next - I gather the SH trees added some new ones for example.
> I'd expect it'll apply after the merge window, if not that's the time to
> look at it.
OK
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: Tue, 10 Jun 2014 02:15:16 +0200 [thread overview]
Message-ID: <1857766.e38RV3V2OT@vostro.rjw.lan> (raw)
In-Reply-To: <20140609225142.GA5099@sirena.org.uk>
On Monday, June 09, 2014 11:51:42 PM Mark Brown wrote:
>
> --fYgRtaZIy+F1uhp1
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> On Tue, Jun 10, 2014 at 12:22:07AM +0200, Rafael J. Wysocki wrote:
> > On Monday, June 09, 2014 08:49:17 PM Mark Brown wrote:
>
> > > Yes, looks like it is.
>
> > But it doesn't apply for me on top of the current Linus' tree.
>
> > Can you please rebase?
>
> It probably depends on other people's trees too, I just killed all the
> usages in -next - I gather the SH trees added some new ones for example.
> I'd expect it'll apply after the merge window, if not that's the time to
> look at it.
OK
next prev parent reply other threads:[~2014-06-09 23: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
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 [this message]
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=1857766.e38RV3V2OT@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.