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]
Date:	Tue, 2 Apr 2013 13:54:51 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Russ Dill <Russ.Dill@...com>
Cc:	Jonghwan Choi <jhbird.choi@...sung.com>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	'Mark Brown' <broonie@...nsource.wolfsonmicro.com>
Subject: Re: [PATCH 3.8-stable] regulator: core: Log when a device causes a
 voltage

On Tue, Apr 02, 2013 at 01:39:06PM -0700, Russ Dill wrote:
> On 04/02/2013 01:02 PM, Greg KH wrote:
> > On Tue, Apr 02, 2013 at 06:30:42PM +0900, Jonghwan Choi wrote:
> >> 3.8-stable review patch.  If anyone has any objections, please let us know.
> >>
> >> ------------------
> >>
> >> From: "Russ Dill <Russ.Dill@...com>"
> >>
> >> commit 6e45eb12fd1c741d556bf264ee98853b5f3104e5 upstream.
> > 
> > Wait, no, this is NOT the commit id of this patch, please don't get this
> > wrong.
> > 
> > I've dropped this from my stable mbox, if Russ feels this should go to
> > 3.8-stable, please send me the correct git id of the patch to apply.
> 
> 9c7b4e8a8ad2624106fbf690fa97ab9c8c9bfa88 is the proper upstream commit.
> This fixes a potential oops that was added in 3.8-rc4, and fixed
> upstream in 3.9-rc1. I do think it belongs in stable.

Thanks, I've applied that commit now.

> Too bad I can't muck up the commit, then I'd owe you a beer. Might help
> that shoulder of yours.

Yes, that would help it out, but probably not help me catch up with
pending patches to apply :)

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ