From: Paul Bolle <pebolle@tiscali.nl>
To: Kukjin Kim <kgene.kim@samsung.com>, Arnd Bergmann <arnd@arndb.de>,
Jason Cooper <jason@lakedaemon.net>
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_SMDKC100
Date: Wed, 02 Jul 2014 10:01:03 +0200 [thread overview]
Message-ID: <1404288063.12021.13.camel@x220> (raw)
Kukjin,
Your commit 52ad6582ceb2 ("ARM: S5PC100: no more support S5PC100 SoC"
landed in next-20140702. It removed the Kconfig symbol MACH_SMDKC100
(and a lot of other stuff).
Is the trivial patch to also remove the last two references to
MACH_SMDKC100 from sound/soc/samsung/Kconfig/ queued somewhere? I don't
think it was part of the series that included the above commit.
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_SMDKC100
Date: Wed, 02 Jul 2014 10:01:03 +0200 [thread overview]
Message-ID: <1404288063.12021.13.camel@x220> (raw)
Kukjin,
Your commit 52ad6582ceb2 ("ARM: S5PC100: no more support S5PC100 SoC"
landed in next-20140702. It removed the Kconfig symbol MACH_SMDKC100
(and a lot of other stuff).
Is the trivial patch to also remove the last two references to
MACH_SMDKC100 from sound/soc/samsung/Kconfig/ queued somewhere? I don't
think it was part of the series that included the above commit.
Paul Bolle
next reply other threads:[~2014-07-02 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 8:01 Paul Bolle [this message]
2014-07-02 8:01 ` ASoC: samsung: MACH_SMDKC100 Paul Bolle
2014-07-18 8:55 ` Paul Bolle
2014-07-18 8:55 ` Paul Bolle
2014-07-18 19:03 ` Kukjin Kim
2014-07-18 19:03 ` Kukjin Kim
2014-09-18 9:55 ` Paul Bolle
2014-09-18 9:55 ` Paul Bolle
2014-09-19 14:30 ` Kukjin Kim
2014-09-19 14:30 ` Kukjin Kim
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=1404288063.12021.13.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=broonie@kernel.org \
--cc=jason@lakedaemon.net \
--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.