From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Taylor Hutt <thutt@chromium.org>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Peter Hsiang <Peter.Hsiang@maxim-ic.com>,
Olof Johansson <olofj@chromium.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: codecs: Max98095: Fix logging of hardware revision.
Date: Wed, 22 Jun 2011 00:28:46 +0100 [thread overview]
Message-ID: <20110621232846.GB8791@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1308596072-17158-1-git-send-email-thutt@chromium.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.
>
> Also, the use of a constant for the length 'max98095_dai' has been
> replaced with ARRAY_SIZE().
Applied. Like I said in my previous mail please do try to split your
patches up better and make sure the changelogs are accurate.
prev parent reply other threads:[~2011-06-21 23:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 18:54 [PATCH] ASoC: codecs: Max98095: Fix logging of hardware revision Taylor Hutt
2011-06-20 20:06 ` Liam Girdwood
2011-06-20 20:06 ` Liam Girdwood
2011-06-21 0:23 ` Mark Brown
2011-06-21 0:23 ` Mark Brown
2011-06-21 0:43 ` Peter Hsiang
2011-06-21 0:43 ` Peter Hsiang
2011-06-21 1:10 ` Mark Brown
2011-06-21 1:10 ` Mark Brown
2011-06-21 11:55 ` Mark Brown
2011-06-21 11:55 ` Mark Brown
2011-06-21 14:52 ` Taylor Hutt
2011-06-21 17:10 ` Mark Brown
2011-06-21 20:16 ` Peter Hsiang
2011-06-21 20:16 ` Peter Hsiang
2011-06-21 20:48 ` Peter Hsiang
2011-06-21 20:48 ` Peter Hsiang
2011-06-21 3:22 ` Taylor Hutt
2011-06-21 10:06 ` Mark Brown
2011-06-21 10:06 ` Mark Brown
2011-06-21 23:28 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110621232846.GB8791@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Peter.Hsiang@maxim-ic.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=olofj@chromium.org \
--cc=perex@perex.cz \
--cc=thutt@chromium.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.