From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jinyoung Park <jinyoungp@nvidia.com>
Cc: 'Peter Hsiang' <Peter.Hsiang@maxim-ic.com>,
"'alsa-devel@alsa-project.org'" <alsa-devel@alsa-project.org>,
swarren@nvidia.com, 'Liam Girdwood' <lrg@slimloigic.co.uk>
Subject: Re: ASoC: codecs: max98088: bug fixes and changes
Date: Wed, 11 May 2011 10:26:46 +0200 [thread overview]
Message-ID: <20110511082646.GA16115@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <D9A2FA38A1E15B4E832469E5FE40C7ABFA0296357B@HKMAIL01.nvidia.com>
On Wed, May 11, 2011 at 02:18:49PM +0800, Jinyoung Park wrote:
> Recently, I working on max98088 and changed something in max98088 asoc driver.
> I included three changes for max98088 in this mail.
> - 1/3 Fixed invalid register definitions in mixer controls
> * This change was confirmed by Peter Hsiang who author of max98088 driver and maxim engineer.
> - 2/3 Moved the EX Limiter Mode from dapm widget to control
> - 3/3 Added digital mute function in DAI1 and DAI2
> Please review below my changes.
Please fix your MUA configuration so you can submit changes as covered
in SubmittingPatches. I've CCed in your colleage Stephen Warren who
seems to have this set up fine. Aside from the HTML issue your mail has
multiple copies of patches in it so it'd be really difficult to apply.
The patches themselves look fine but please resend in a format that's
easier to apply.
prev parent reply other threads:[~2011-05-11 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 6:18 ASoC: codecs: max98088: bug fixes and changes Jinyoung Park
2011-05-11 6:22 ` FW: " Jinyoung Park
2011-05-11 6:23 ` Jinyoung Park
2011-05-11 8:26 ` 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=20110511082646.GA16115@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Peter.Hsiang@maxim-ic.com \
--cc=alsa-devel@alsa-project.org \
--cc=jinyoungp@nvidia.com \
--cc=lrg@slimloigic.co.uk \
--cc=swarren@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).