From: Arun KS <getarunks@gmail.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>
Subject: Re: Beep sound in the end of audio file
Date: Thu, 7 May 2009 15:05:08 +0530 [thread overview]
Message-ID: <dfeb90390905070235i47f9aed4lbd2298ba07a5b989@mail.gmail.com> (raw)
In-Reply-To: <20090506140719.GF6573@sirena.org.uk>
On Wed, May 6, 2009 at 7:37 PM, Mark Brown <broonie@sirena.org.uk> wrote:
> On Wed, May 06, 2009 at 07:30:03PM +0530, Aggarwal, Anuj wrote:
>
>> > After a quick look I can not pin point the soc board file used with the
>> > omap3evm board. Is it in the tree?
>
>> [Aggarwal, Anuj] No, it is not. Reason being we already have beagle &
>> sdp3430 there, which are both similar to omap3evm, which I pushed.
>> So mine got rejected. We had some discussions on how to handle this
>> scenario but nothing got finalized.
>
> Not from the ALSA side it didn't...
Mark,
Since we are not going with the generic driver, are you going to push
this patch:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg07166.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-05-07 9:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 17:03 Beep sound in the end of audio file Aggarwal, Anuj
2009-05-06 5:33 ` Peter Ujfalusi
2009-05-06 14:00 ` Aggarwal, Anuj
2009-05-06 14:07 ` [alsa-devel] " Mark Brown
2009-05-07 9:35 ` Arun KS [this message]
2009-05-07 9:38 ` Mark Brown
2009-05-07 10:48 ` Arun KS
2009-05-06 14:19 ` Todd Fischer
2009-05-07 5:48 ` Peter Ujfalusi
2009-05-07 11:08 ` Peter Ujfalusi
2009-05-07 11:16 ` Aggarwal, Anuj
2009-05-07 11:24 ` Peter Ujfalusi
2009-05-07 12:48 ` Arun KS
2009-05-07 14:15 ` Jarkko Nikula
2009-05-06 14:01 ` Jon Smirl
2009-05-06 14:03 ` [alsa-devel] " Jon Smirl
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=dfeb90390905070235i47f9aed4lbd2298ba07a5b989@mail.gmail.com \
--to=getarunks@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=broonie@sirena.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.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