From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [PATCH v2 6/6] mmc: omap_hsmmc: Don't expect MMC1 to always have vmmc supply Date: Tue, 21 Feb 2012 12:20:22 +0000 Message-ID: <20120221122022.GC22675@n2100.arm.linux.org.uk> References: <1329818589-10062-1-git-send-email-rnayak@ti.com> <1329818589-10062-7-git-send-email-rnayak@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org To: "S, Venkatraman" Cc: Rajendra Nayak , cjb@laptop.org, linaro-dev@lists.linaro.org, balajitk@ti.com, linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-Id: linux-omap@vger.kernel.org On Tue, Feb 21, 2012 at 05:43:54PM +0530, S, Venkatraman wrote: > On Tue, Feb 21, 2012 at 3:33 PM, Rajendra Nayak wrote= : > > @@ -324,8 +302,8 @@ static int omap_hsmmc_reg_get(struct omap_hsmmc= _host > > *host) > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mmc_slot(host).ocr_m= ask =3D ocr_value; > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0} else { > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if (!(mmc_slot(host)= =2Eocr_mask & ocr_value)) { > > - =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 pr_er= r("MMC%d ocrmask %x is not > > supported\n", > > - =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 host->id, > > mmc_slot(host).ocr_mask); > > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 pr_er= r("MMC ocrmask %x is not > > supported\n", > > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 mmc_slot(host).ocr_mask); You're dropping the MMC number from these error messages. It would be much better to fix them instead. Use dev_info(mmc_dev(host->mmc), "bla= h" rather than pr_err(). Drivers should not be using pr_* unless they really do not have a struc= t device.