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: <20140220003639.GF2669@sirena.org.uk>
Date:	Thu, 20 Feb 2014 09:36:39 +0900
From:	Mark Brown <broonie@...nel.org>
To:	Shuah Khan <shuah.kh@...sung.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, stable@...r.kernel.org,
	"shuahkhan@...il.com" <shuahkhan@...il.com>
Subject: Re: [PATCH 3.13 00/40] 3.13.4-stable review

On Wed, Feb 19, 2014 at 05:16:22PM -0700, Shuah Khan wrote:

> On Intel systems, there are no dmesg regressions: emerg, crit,
> alert, err are clean. No regressions in warn.

> On AMD systems, the following new error messages - suspect is to
> drivers/regulator/core.c - patch

> 3.13.4 - amd:
> > sdhci-pci 0000:02:00.1: dummy supplies not allowed
> > sdhci-pci 0000:02:00.1: dummy supplies not allowed
> drivers/regulator/core.c - patch

This is nothing to do with AMD or Intel, it's to do with if your system
has a sdhci-pci device in it.  This shouldn't result in a change in
actual behaviour, it's just a warning caused by the fact that we now do
provide dummies for other devices.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ