Re: [PATCH RESEND] driver core: always handle dpm_order

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Mon, May 28, 2012 at 02:38:09PM +0800, Linus Walleij wrote:
> On Tue, Apr 24, 2012 at 10:36 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Tue, Apr 24, 2012 at 02:11:09PM +0200, Linus Walleij wrote:
> >> On Mon, Apr 23, 2012 at 5:43 PM, Greg Kroah-Hartman
> >> <gregkh@linuxfoundation.org> wrote:
> >> > On Mon, Apr 23, 2012 at 09:16:36AM +0200, 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.
> >> >>
> >> >> Cc: Rafael J. Wysocki <rjw@sisk.pl>
> >> >> Signed-off-by: Rabin Vincent <rabin.vincent@stericsson.com>
> >> >> Reviewed-by: Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>
> >> >> [Fixed a small dangling label compile warning]
> >> >> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> >> >> ---
> >> >>  drivers/base/core.c |   36 ++++++++++++++++++------------------
> >> >>  1 file changed, 18 insertions(+), 18 deletions(-)
> >> >
> >> > Is this a problem in 3.4?  Older kernels?  Or can it wait for 3.5?
> >>
> >> Rabin said earlier that it could wait for 3.4 atleast.
> >
> > That didn't answer my question at all.  Oh well, 3.5 it is...
> 
> Is this going upstream in this merge window? I haven't seen it
> in Torvalds' tree, but I guess it may be pending for a late
> merge...?

Nope, it missed 3.5 as no one ever answered my questions, so I guessed
that no one really cares about this :(

greg k-h