linux-kernel - Re: [PATCH] driver core: always handle dpm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120410143633.GB14703@kroah.com>
Date:	Tue, 10 Apr 2012 07:36:33 -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,
	Rabin Vincent <rabin.vincent@...ricsson.com>
Subject: Re: [PATCH] driver core: always handle dpm_order

On Tue, Apr 10, 2012 at 12:51:35PM +0200, Linus Walleij wrote:
> On Thu, Mar 15, 2012 at 4:43 PM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > On Thu, Mar 15, 2012 at 10:58:18AM +0100, 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.
> >
> > Is there code today in the kernel that needs this to go in now?  For
> > older releases?  Or is 3.4 acceptable?
> 
> To me it seems it has not been merged to 3.4 yet ... can we have it
> for the -rc:s?

Does it fix a bug somewhere?  If so, sure, but I didn't get the
impression that it did, and as it came after the merge window, I was
going to wait.

If this is incorrect, please let me know.

thanks,

greg k-h
--
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/