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, "Rafael J. Wysocki" <rjw@sisk.pl>,
Rabin Vincent <rabin.vincent@stericsson.com>
Subject: Re: [PATCH RESEND] driver core: always handle dpm_order
Date: Tue, 24 Apr 2012 07:36:24 -0700 [thread overview]
Message-ID: <20120424143624.GB3438@kroah.com> (raw)
In-Reply-To: <CACRpkdabgGFCLGNFtje2efXoRHtk_uvb3yo6FTkH2pVGpHGB1A@mail.gmail.com>
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...
next prev parent reply other threads:[~2012-04-24 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 7:16 Linus Walleij
2012-04-23 11:47 ` Rafael J. Wysocki
2012-04-23 15:43 ` Greg Kroah-Hartman
2012-04-24 12:11 ` Linus Walleij
2012-04-24 14:36 ` Greg Kroah-Hartman [this message]
2012-05-28 6:38 ` Linus Walleij
2012-05-28 7:14 ` Greg Kroah-Hartman
2012-05-28 9:33 ` Linus Walleij
2012-06-11 16:30 ` Linus Walleij
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=20120424143624.GB3438@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 \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®