From: Frank Mandarino <fmandarino@endrelia.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Sedji Gaouaou <sedji.gaouaou@atmel.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@sirena.org.uk>
Subject: Re: [PATCH] ASoC: Remove references to Endrelia ETI-B1 board
Date: Tue, 30 Sep 2008 11:12:02 -0400 [thread overview]
Message-ID: <48E241C2.2070906@endrelia.com> (raw)
In-Reply-To: <s5hy719fzt6.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Tue, 30 Sep 2008 10:42:40 -0400,
> Frank Mandarino wrote:
>> The ASoC machine drivers for this board were only provided as examples
>> for the new AT91 ASoC platform driver. Since the ETI-B1 board is
>> proprietary and there are other AT91 ASoC machine drivers available,
>> it makes sense to remove these drivers.
>>
>> Signed-off-by: Frank Mandarino <fmandarino@endrelia.com>
>> ---
>> sound/soc/at91/Kconfig | 27 ---
>> sound/soc/at91/Makefile | 7 -
>> sound/soc/at91/eti_b1_bluecore.c | 284 -------------------------------
>> sound/soc/at91/eti_b1_wm8731.c | 350 --------------------------------------
>
> Note that eti_b1_bluecore isn't in the current ALSA tree.
>
>
> thanks,
>
> Takashi
Yes, I realize this. I created the patch against the dev branch of the
ASoC git repository, where eti_b1_bluecore does exist.
Mark: is this a problem? Should I create a patch against the ASoC
"master" branch?
../fam
--
Frank Mandarino fmandarino@endrelia.com
Endrelia Technologies Inc.
Toronto, Ontario, Canada
416.208.6986 x4522
next prev parent reply other threads:[~2008-09-30 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 14:42 [PATCH] ASoC: Remove references to Endrelia ETI-B1 board Frank Mandarino
2008-09-30 14:46 ` Mark Brown
2008-09-30 14:55 ` Takashi Iwai
2008-09-30 15:12 ` Frank Mandarino [this message]
2008-09-30 18:12 ` Mark Brown
2008-09-30 15:10 ` Jarkko Nikula
2008-09-30 15:39 ` Frank Mandarino
2008-09-30 18:25 ` Mark Brown
2008-10-01 6:15 ` Jarkko Nikula
2008-09-30 15:11 ` Alan Horstmann
2008-09-30 15:30 ` Frank Mandarino
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=48E241C2.2070906@endrelia.com \
--to=fmandarino@endrelia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=sedji.gaouaou@atmel.com \
--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.