public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
	linux-kernel@vger.kernel.org,
	Rabin Vincent <rabin.vincent@stericsson.com>
Subject: Re: [PATCH] driver core: always handle dpm_order
Date: Tue, 10 Apr 2012 07:36:33 -0700	[thread overview]
Message-ID: <20120410143633.GB14703@kroah.com> (raw)
In-Reply-To: <CACRpkdaLhdjOU0CUfR3SWbDzB9qRLqBpBz+zUwPf_Q5Bu2otow@mail.gmail.com>

On Tue, Apr 10, 2012 at 12:51:35PM +0200, Linus Walleij wrote:
> On Thu, Mar 15, 2012 at 4:43 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Thu, Mar 15, 2012 at 10:58:18AM +0100, Linus Walleij wrote:
> >> From: Rabin Vincent <rabin.vincent@stericsson.com>
> >>
> >> If !dev->class, device_move() does not respect the dpm_order.
> >> Fix it to do so.
> >
> > Is there code today in the kernel that needs this to go in now?  For
> > older releases?  Or is 3.4 acceptable?
> 
> To me it seems it has not been merged to 3.4 yet ... can we have it
> for the -rc:s?

Does it fix a bug somewhere?  If so, sure, but I didn't get the
impression that it did, and as it came after the merge window, I was
going to wait.

If this is incorrect, please let me know.

thanks,

greg k-h

  reply	other threads:[~2012-04-10 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  9:58 [PATCH] driver core: always handle dpm_order Linus Walleij
2012-03-15 15:43 ` Greg Kroah-Hartman
2012-03-19  8:30   ` Rabin Vincent
2012-04-10 10:51   ` Linus Walleij
2012-04-10 14:36     ` Greg Kroah-Hartman [this message]
2012-04-11  7:24       ` Linus Walleij
2012-04-10 22:21     ` Rafael J. Wysocki
2012-04-11  7:20       ` Linus Walleij
2012-04-18 20:01         ` Greg Kroah-Hartman

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=20120410143633.GB14703@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rabin.vincent@stericsson.com \
    /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