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

[Linus Walleij]

On Tue, Apr 24, 2012 at 10:36 PM, Greg Kroah-Hartman
<gregkh@xxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx> wrote:
>> > On Mon, Apr 23, 2012 at 09:16:36AM +0200, Linus Walleij wrote:
>> >> From: Rabin Vincent <rabin.vincent@xxxxxxxxxxxxxx>
>> >>
>> >> If !dev->class, device_move() does not respect the dpm_order.
>> >> Fix it to do so.
>> >>
>> >> Cc: Rafael J. Wysocki <rjw@xxxxxxx>
>> >> Signed-off-by: Rabin Vincent <rabin.vincent@xxxxxxxxxxxxxx>
>> >> Reviewed-by: Srinidhi Kasagar <srinidhi.kasagar@xxxxxxxxxxxxxx>
>> >> [Fixed a small dangling label compile warning]
>> >> Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx>
>> >> ---
>> >>  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...?

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/