From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Philipp Zabel <philipp.zabel@gmail.com>
Subject: Re: [PATCH] ASoC: build fix for snd_soc_info_bool_ext
Date: Tue, 13 May 2008 13:07:52 +0200 [thread overview]
Message-ID: <s5hod7aea2f.wl%tiwai@suse.de> (raw)
In-Reply-To: <20080510143732.GA7124@sirena.org.uk>
At Sat, 10 May 2008 15:37:36 +0100,
Mark Brown wrote:
>
> On Sat, May 10, 2008 at 02:07:39PM +0200, Philipp Zabel wrote:
>
> > ???I suspect that ???snd_ctl_boolean_mono should have been
> > snd_ctl_boolean_mono_info instead. This fixes the build for magician.
>
> > Signed-off-by: Philipp Zabel <philipp.zabel@gmail.com>
>
> Looks like you're right there - thanks.
>
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Applied to ALSA tree now.
thanks,
Takashi
prev parent reply other threads:[~2008-05-13 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 12:07 [PATCH] ASoC: build fix for snd_soc_info_bool_ext Philipp Zabel
2008-05-10 14:37 ` Mark Brown
2008-05-13 11:07 ` Takashi Iwai [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=s5hod7aea2f.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=philipp.zabel@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