From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH] ASoC: codecs: Max98095: Fix logging of hardware revision. Date: Tue, 21 Jun 2011 01:23:39 +0100 Message-ID: <20110621002322.GE1905@opensource.wolfsonmicro.com> References: <1308596072-17158-1-git-send-email-thutt@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource2.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 0CB2D244A2 for ; Tue, 21 Jun 2011 02:23:42 +0200 (CEST) Content-Disposition: inline In-Reply-To: <1308596072-17158-1-git-send-email-thutt@chromium.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Taylor Hutt Cc: alsa-devel@alsa-project.org, Takashi Iwai , linux-kernel@vger.kernel.org, Peter Hsiang , Olof Johansson , Liam Girdwood List-Id: alsa-devel@alsa-project.org On Mon, Jun 20, 2011 at 11:54:32AM -0700, Taylor Hutt wrote: > The base hardware revision of the Maxim 98095 part is 0x40; the code > which outputs the revision of the hardware has been updated to > properly use uppercase alphabetic values for the revision numbers. Are you sure that this is true for all devices that might be supported by the driver (I'm guessing there may be other variants)? There's often a drift between silicon and package revisions which gets papered over by datasheets and ignored by drivers. > Also, the use of a constant for the length 'max98095_dai' has been > replaced with ARRAY_SIZE(). Don't include a series of random unrelated changes in a single patch, split them up into separate patches. This makes review much easier if nothing else. There's no overlap at all between this change and the one above. The change is sensible. > ret = snd_soc_read(codec, M98095_0FF_REV_ID); > if (ret < 0) { > - dev_err(codec->dev, "Failed to read device revision: %d\n", > + dev_err(codec->dev, "Failure reading hardware revision: %d\n", > ret); You've also got this again unrelated change which isn't mentioned in the changelog at all.