From: Kukjin Kim <kgene@kernel.org>
To: 'Paul Bolle' <pebolle@tiscali.nl>
Cc: 'Arnd Bergmann' <arnd@arndb.de>,
'Jason Cooper' <jason@lakedaemon.net>,
'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: RE: ASoC: samsung: MACH_SMDKC100
Date: Fri, 19 Sep 2014 23:30:17 +0900 [thread overview]
Message-ID: <017301cfd416$3bf90be0$b3eb23a0$@kernel.org> (raw)
In-Reply-To: <1411034122.2017.18.camel@x220>
Paul Bolle wrote:
>
> Hi Kukjin,
>
Hi,
> On Sat, 2014-07-19 at 04:03 +0900, Kukjin Kim wrote:
> > On 07/18/14 17:55, Paul Bolle wrote:
> > > On Wed, 2014-07-02 at 10:01 +0200, Paul Bolle wrote:
> > >> 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.
> > >
> > > Have you had time to look at this? Those last two references to
> > > MACH_SMDKC100 can still be seen in next-20140718.
> > >
> > Yeah you're right. The MACH_SMDKC100 is no more required...
> >
> > I submitted its fixup to Mark and I think he will take it for v3.17.
>
> What ever happened to that fixup? There are still (pointless) references
> to MACH_SMDKC100 in v3.17-rc5 and in next-20140918.
>
Oh....Mark, what's wrong?
- Kukjin
prev parent reply other threads:[~2014-09-19 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 8:01 ASoC: samsung: MACH_SMDKC100 Paul Bolle
2014-07-18 8:55 ` Paul Bolle
2014-07-18 19:03 ` Kukjin Kim
2014-09-18 9:55 ` Paul Bolle
2014-09-19 14:30 ` Kukjin Kim [this message]
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='017301cfd416$3bf90be0$b3eb23a0$@kernel.org' \
--to=kgene@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=broonie@kernel.org \
--cc=jason@lakedaemon.net \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).