[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120424143624.GB3438@kroah.com>
Date: Tue, 24 Apr 2012 07:36:24 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Linus Walleij <linus.walleij@...ricsson.com>,
linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>,
Rabin Vincent <rabin.vincent@...ricsson.com>
Subject: Re: [PATCH RESEND] driver core: always handle dpm_order
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@...uxfoundation.org> wrote:
> > On Mon, Apr 23, 2012 at 09:16:36AM +0200, Linus Walleij wrote:
> >> From: Rabin Vincent <rabin.vincent@...ricsson.com>
> >>
> >> If !dev->class, device_move() does not respect the dpm_order.
> >> Fix it to do so.
> >>
> >> Cc: Rafael J. Wysocki <rjw@...k.pl>
> >> Signed-off-by: Rabin Vincent <rabin.vincent@...ricsson.com>
> >> Reviewed-by: Srinidhi Kasagar <srinidhi.kasagar@...ricsson.com>
> >> [Fixed a small dangling label compile warning]
> >> Signed-off-by: Linus Walleij <linus.walleij@...aro.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...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists