From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-id: <5305584D.9030106@samsung.com> Date: Wed, 19 Feb 2014 18:20:13 -0700 From: Shuah Khan Reply-to: shuah.kh@samsung.com MIME-version: 1.0 To: Mark Brown Cc: Greg Kroah-Hartman , linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, stable@vger.kernel.org, "shuahkhan@gmail.com" Subject: Re: [PATCH 3.13 00/40] 3.13.4-stable review References: <20140218224433.337299968@linuxfoundation.org> <53054956.4010602@samsung.com> <20140220003639.GF2669@sirena.org.uk> In-reply-to: <20140220003639.GF2669@sirena.org.uk> Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 02/19/2014 05:36 PM, Mark Brown wrote: > 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. > Right. I think this message should be a warning instead of an error. Error is too alarming, unless there is a good reason for it to be an error. -- Shuah -- Shuah Khan Senior Linux Kernel Developer - Open Source Group Samsung Research America(Silicon Valley) shuah.kh@samsung.com | (970) 672-0658