From: Paul Bolle <pebolle@tiscali.nl>
To: Mark Brown <broonie@kernel.org>
Cc: Kukjin Kim <kgene@kernel.org>, Sangbeom Kim <sbkim73@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-samsung-soc@vger.kernel.org, alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] ASoC: samsung: clean up references to outdated Kconfig symbols
Date: Sat, 07 Feb 2015 09:38:04 +0100 [thread overview]
Message-ID: <1423298284.2246.5.camel@x220> (raw)
In-Reply-To: <20150206235044.GO31311@finisterre.sirena.org.uk>
On Sat, 2015-02-07 at 07:50 +0800, Mark Brown wrote:
> On Mon, Jan 19, 2015 at 11:41:07AM +0100, Paul Bolle wrote:
> > A few series of ARM cleanups regarding S5PC100 and S5PV210 were included
> > in v3.17. These series removed these five Kconfig symbols:
> > MACH_AQUILA
> > MACH_GONI
> > MACH_SMDKC100
> > MACH_SMDKC110
> > MACH_SMDKV210
> >
> > This series, done on top of next-20150119, removes the remaining
>
> If you are posting a patch series please ensure that all the patches in
> the series are threaded in reply to the cover letter (or first patch if
> there isn't one) so that mail clients can see to display them as a
> series.
Patches 2/4, 3/4, and 4/4 didn't apply. Locally I carry them in a tree
that constantly rebases on top of linux-next. So locally I carry these
patches on top of next-20150204.
What tree would you like me to rebase this onto?
Paul Bolle
next prev parent reply other threads:[~2015-02-07 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 10:41 [PATCH 0/4] ASoC: samsung: clean up references to outdated Kconfig symbols Paul Bolle
2015-02-06 23:50 ` Mark Brown
2015-02-07 8:38 ` Paul Bolle [this message]
2015-02-09 6:07 ` Mark Brown
2015-02-11 9:21 ` Paul Bolle
2015-02-14 4:22 ` 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=1423298284.2246.5.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kgene@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sbkim73@samsung.com \
--cc=tiwai@suse.de \
--cc=valentinrothberg@gmail.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 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).