From: Paul Bolle <pebolle@tiscali.nl>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: Ben Dooks <ben-linux@fluff.org>,
Sangbeom Kim <sbkim73@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.de>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, alsa-devel@alsa-project.org
Subject: ASoC: samsung: MACH_SMDK6450
Date: Wed, 02 Jul 2014 09:47:18 +0200 [thread overview]
Message-ID: <1404287238.12021.7.camel@x220> (raw)
Kukjin,
Your commit 0aeaa68cf509 ("ASoC: samsung: no more support for S5P6440
and S5P6450 SoCs") landed in next-20140702. It removed references to
MACH_SMDK6440 and MACH_SMDK6450 from sound/soc/samsung/.
It seems to have missed one reference to MACH_SMDK6450 in
sound/soc/samsung/Kconfig (an optional dependency of
SND_SOC_SMDK_WM8580_PCM). Is the oneliner to remove that optional
dependency queued somewhere?
Paul Bolle
WARNING: multiple messages have this Message-ID (diff)
From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: ASoC: samsung: MACH_SMDK6450
Date: Wed, 02 Jul 2014 09:47:18 +0200 [thread overview]
Message-ID: <1404287238.12021.7.camel@x220> (raw)
Kukjin,
Your commit 0aeaa68cf509 ("ASoC: samsung: no more support for S5P6440
and S5P6450 SoCs") landed in next-20140702. It removed references to
MACH_SMDK6440 and MACH_SMDK6450 from sound/soc/samsung/.
It seems to have missed one reference to MACH_SMDK6450 in
sound/soc/samsung/Kconfig (an optional dependency of
SND_SOC_SMDK_WM8580_PCM). Is the oneliner to remove that optional
dependency queued somewhere?
Paul Bolle
next reply other threads:[~2014-07-02 7:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 7:47 Paul Bolle [this message]
2014-07-02 7:47 ` ASoC: samsung: MACH_SMDK6450 Paul Bolle
2014-07-02 9:23 ` Mark Brown
2014-07-02 9:23 ` Mark Brown
2014-07-02 22:37 ` Kukjin Kim
2014-07-02 22:37 ` Kukjin Kim
2014-07-03 11:14 ` Mark Brown
2014-07-03 11:14 ` Mark Brown
2014-07-04 0:39 ` Kukjin Kim
2014-07-04 0:39 ` Kukjin Kim
2014-07-04 3:39 ` Olof Johansson
2014-07-04 3:39 ` Olof Johansson
2014-07-04 9:01 ` Arnd Bergmann
2014-07-04 9:01 ` Arnd Bergmann
2014-07-04 11:45 ` Mark Brown
2014-07-04 11:45 ` 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=1404287238.12021.7.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@kernel.org \
--cc=kgene.kim@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sbkim73@samsung.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.