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

From: Linus Walleij
Date: Tue Apr 24 2012 - 08:11:14 EST


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.

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/