From: Mark Brown <broonie@sirena.org.uk>
To: Jinyoung Park <mcjin02@gmail.com>
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: errors in wm8990 codec driver
Date: Thu, 30 Apr 2009 11:23:01 +0100 [thread overview]
Message-ID: <20090430102301.GF10190@sirena.org.uk> (raw)
In-Reply-To: <280b69ac0904292203y11c100f8m658a3579c33e8534@mail.gmail.com>
On Thu, Apr 30, 2009 at 02:03:03PM +0900, Jinyoung Park wrote:
> I found a number of typing errors in wm8990 codec driver.
> The mis-typing exist in dapm controller definitions and dapm route definitions,
> so happen mis-matched error when snd_soc_dapm_add_routes().
> Belows are my modified code. Please check...
This all looks reasonable - could you please supply a Signed-off-by for
your patch? It may also help to use git send-email to send your patch
or attach it, gmail tends to mangle patches so that they can't be
applied and it looks like some of that may have happened here, though
I've not actually tried applying it.
next prev parent reply other threads:[~2009-04-30 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 5:03 errors in wm8990 codec driver Jinyoung Park
2009-04-30 10:23 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-01 2:02 Park Jinyoung
2009-05-01 11:57 ` Mark Brown
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=20090430102301.GF10190@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=mcjin02@gmail.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