linux-kernel - Re: [PATCH, RESEND] Putting the device into runtime suspend after resume()/probe() is handled

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] [day] [month] [year] [list]

Message-Id: <20110309140712.2500862d.akpm@linux-foundation.org>
Date:	Wed, 9 Mar 2011 14:07:12 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org, Hong Liu <hong.liu@...el.com>
Subject: Re: [PATCH, RESEND] Putting the device into runtime suspend after
 resume()/probe() is handled

On Wed, 9 Mar 2011 21:59:32 +0000
Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> On Wed, 9 Mar 2011 13:45:04 -0800
> Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
> > On Wed, 09 Mar 2011 12:39:34 +0000
> > Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > 
> > > From: Alan Cox <alan@...rguk.ukuu.org.uk>
> > > To: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
> > > Subject: [PATCH, RESEND] Putting the device into runtime suspend after resume()/probe() is handled
> > > Date: Wed, 09 Mar 2011 12:39:34 +0000
> > > User-Agent: StGIT/0.14.3
> > > 
> > > From: Hong Liu <hong.liu@...el.com>
> > > 
> > > by the PM core and the device core code. No need to manually add them in
> > > each single driver. And correct the runtime state in remove().
> > > 
> > > Signed-off-by: Hong Liu <hong.liu@...el.com>
> > > Signed-off-by: Alan Cox <alan@...ux.intel.com>
> > 
> > I'd merged this a while back but was awaiting info on why v1 had a
> > cc:stable so the changelog could be updated to indicate why a -stable
> > backport was needed.
> > 
> > I see that the cc:stable has been removed so that settles that.  But
> > it's still unclear how serious the bugs-which-were fixed are.  Oh well,
> > a bug's a bug.  I put it in my 2.6.38 queue anyway.
> 
> Don't think anything there is that important. Also anyone actually using
> the driver would I'm pretty sure currently be running an Intel spun
> kernel not a generic 2.6.older unless someone is also now relying on it
> for another platform anyway.

OK, thanks.  Let's shoot for 2.6.39 then.
--
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/