All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Shunli Wang <shunli.wang@mediatek.com>
Cc: alsa-devel@alsa-project.org, garlic.tseng@mediatek.com,
	linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com,
	kaichieh.chuang@mediatek.com
Subject: Re: [PATCH 5/6] ASoC: mediatek: mt8183: add mt8183-mt6358 machine driver
Date: Fri, 25 Jan 2019 18:10:46 +0000	[thread overview]
Message-ID: <20190125181046.GC6939@sirena.org.uk> (raw)
In-Reply-To: <1548139153-18783-6-git-send-email-shunli.wang@mediatek.com>


[-- Attachment #1.1: Type: text/plain, Size: 878 bytes --]

On Tue, Jan 22, 2019 at 02:39:12PM +0800, Shunli Wang wrote:
> The board uses mt8183 as SoC and codec as mt6358.
> Between SoC and codec, a mtk-properity audio inferface
> is used.

This one also breaks the build:

Applying patch #10781729 using 'git am -3 -s'
Description: [5/6] ASoC: mediatek: mt8183: add mt8183-mt6358 machine driver
Applying: ASoC: mediatek: mt8183: add mt8183-mt6358 machine driver
scripts/kconfig/conf  --oldconfig Kconfig
sound/soc/mediatek/Kconfig:119:error: recursive dependency detected!
sound/soc/mediatek/Kconfig:119:	symbol SND_SOC_MT8183_MT6358 depends on SND_SOC_MT8183
sound/soc/mediatek/Kconfig:109:	symbol SND_SOC_MT8183 is selected by SND_SOC_MT8183_MT6358
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"

make[1]: *** [scripts/kconfig/Makefile:69: oldconfig] Error 1

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2019-01-25 18:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22  6:39 [PATCH 0/6] ASoC: Mediatek: Add support for MT8183 AoC and MT6358 Codec Shunli Wang
     [not found] ` <1548139153-18783-1-git-send-email-shunli.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-01-22  6:39   ` [PATCH 1/6] ASoC: mediatek: mt8183: add platform driver Shunli Wang
     [not found]     ` <1548139153-18783-2-git-send-email-shunli.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-01-25 18:11       ` Applied "ASoC: mediatek: mt8183: add platform driver" to the asoc tree Mark Brown
2019-01-22  6:39   ` [PATCH 2/6] ASoC: mediatek: mt8183: add audio afe document Shunli Wang
2019-01-25 18:11     ` Applied "ASoC: mediatek: mt8183: add audio afe document" to the asoc tree Mark Brown
2019-01-22  6:39   ` [PATCH 3/6] ASoC: mediatek: mt6358: add codec driver Shunli Wang
2019-01-25 18:10     ` Mark Brown
2019-01-25 18:11     ` Applied "ASoC: mediatek: mt6358: add codec driver" to the asoc tree Mark Brown
2019-01-22  6:39   ` [PATCH 4/6] ASoC: mediatek: mt6358: add codec document Shunli Wang
2019-01-25 18:11     ` Applied "ASoC: mediatek: mt6358: add codec document" to the asoc tree Mark Brown
2019-01-22  6:39   ` [PATCH 5/6] ASoC: mediatek: mt8183: add mt8183-mt6358 machine driver Shunli Wang
2019-01-25 18:10     ` Mark Brown [this message]
2019-01-22  6:39   ` [PATCH 6/6] ASoC: mediatek: add document for mt8183-mt6358 Shunli Wang

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=20190125181046.GC6939@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=garlic.tseng@mediatek.com \
    --cc=kaichieh.chuang@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=shunli.wang@mediatek.com \
    --cc=wsd_upstream@mediatek.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.