From: Sangbeom Kim <sbkim73@samsung.com>
To: 'Mark Brown' <broonie@opensource.wolfsonmicro.com>,
'Liam Girdwood' <lrg@ti.com>,
'Jassi Brar' <jassisinghbrar@gmail.com>
Cc: '김국진' <kgene.kim@samsung.com>,
alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: Revert "ASoC: SAMSUNG: Add I2S0 internal dma driver"
Date: Fri, 22 Jul 2011 13:31:19 +0900 [thread overview]
Message-ID: <039f01cc4828$34618600$9d249200$@com> (raw)
In-Reply-To: <1311266209-14505-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On 22/07/11 1:37 AM, Mark Brown wrote:
> This reverts commit d7c3e9525ac8e898f1156a1f3a7c5038f6560186 as it does
> not currently build due to missing dependencies in the Samsung tree.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
(Cc'ed Kukjin Kim on this)
I'm sorry that I missed the clarification of code dependency.
I will try to clarify code dependency in the next time.
idma code have dependency on
ARM: SAMSUNG: Add IRQ_I2S0 definition
(commit ID: 2d21237e38120c2dfbc047b39aa2a56df67bdeec)
ARM: SAMSUNG: Add platform device for idma
(commit ID: 2839cc1e7e1f260afc5cf9fb6be5b6c3e9d85fea)
Above 2 commits had already merged on Kukjin kim's tree and then
Merged on arm-soc.
Currently, There is no topic branch for idma on Kukjin's tree.
So If you need it, You need to merge next-samsung-devel branch on Kukjin's
tree.
But It have many other Samsung stuff.
What should I do?
Thanks,
SB Kim
next prev parent reply other threads:[~2011-07-22 4:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 16:36 [PATCH] ASoC: Revert "ASoC: SAMSUNG: Add I2S0 internal dma driver" Mark Brown
2011-07-21 18:05 ` Liam Girdwood
2011-07-22 3:12 ` Jassi Brar
2011-07-22 4:31 ` Sangbeom Kim [this message]
2011-07-22 9:54 ` Mark Brown
2011-08-11 6:24 ` Kukjin Kim
2011-08-11 9:10 ` Mark Brown
2011-08-12 1:02 ` 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='039f01cc4828$34618600$9d249200$@com' \
--to=sbkim73@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassisinghbrar@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=lrg@ti.com \
--cc=patches@opensource.wolfsonmicro.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 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.