All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	paul@pwsan.com, gregkh@suse.de, linux-kernel@vger.kernel.org,
	linux-pm@lists.linux-foundation.org
Subject: Re: [linux-pm] [PATCH] Driver Core: Add platform device arch data V3
Date: Fri, 26 Jun 2009 02:17:28 +0900	[thread overview]
Message-ID: <20090625171728.GA25320@linux-sh.org> (raw)
In-Reply-To: <200906251634.12222.rjw@sisk.pl>

On Thu, Jun 25, 2009 at 04:34:11PM +0200, Rafael J. Wysocki wrote:
> On Thursday 25 June 2009, Magnus Damm wrote:
> > If possible, I'd like this to be merged as early as possible since a
> > lot of processor specific changes will depend on it. With this
> > included in 2.6.31 I can easily build arch specific code for 2.6.32.
> > Anything I can do to make that happen?
> > 
> > My top priority is Runtime PM for SuperH on top of your code, and I
> > intend to post a prototype for SuperH before the PM Summit. It would
> > be great to minimize the dependencies though, and including this in
> > 2.6.31 would certainly help.
> 
> I'm going to add this patch to my linux-next branch shortly and if your 2.6.32
> development is based on that branch (I'd recommend that anyway), there
> shouldn't be any problems during the 2.6.32 merge window.
> 
Yes, I was already planning on creating a topic branch based off of this
so that we can start getting things ready in the sh tree, so this is not
a problem.. as long as you don't rebase ;-)

  parent reply	other threads:[~2009-06-25 17:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 12:16 [PATCH] Driver Core: Add platform device arch data V3 Magnus Damm
2009-06-18 16:21 ` Kevin Hilman
2009-06-18 16:21   ` Kevin Hilman
2009-06-24 11:50   ` Magnus Damm
2009-06-24 11:50     ` Magnus Damm
2009-06-24 18:50     ` Rafael J. Wysocki
2009-06-24 18:50     ` Rafael J. Wysocki
2009-06-25  2:25       ` Magnus Damm
2009-06-25  2:25         ` Magnus Damm
2009-06-25 14:34         ` Rafael J. Wysocki
2009-06-25 14:34           ` Rafael J. Wysocki
2009-06-25 17:17           ` Paul Mundt
2009-06-25 17:17           ` Paul Mundt [this message]
2009-06-25 14:35   ` Rafael J. Wysocki
2009-06-25 14:35     ` Rafael J. Wysocki
2009-06-25 15:30     ` Greg KH
2009-06-25 15:30     ` Greg KH
2009-07-04 23:44 ` Rafael J. Wysocki
2009-07-04 23:44   ` 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=20090625171728.GA25320@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=magnus.damm@gmail.com \
    --cc=paul@pwsan.com \
    --cc=rjw@sisk.pl \
    /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.