From: Andrew Lunn <andrew@lunn.ch>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
alsa-devel@alsa-project.org, Jason Cooper <jason@lakedaemon.net>,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 03/12] ASoC: kirkwood: Remove unused drivers
Date: Tue, 29 Jul 2014 22:48:53 +0200 [thread overview]
Message-ID: <20140729204853.GC17763@lunn.ch> (raw)
In-Reply-To: <20140729193509.GK17528@sirena.org.uk>
On Tue, Jul 29, 2014 at 08:35:09PM +0100, Mark Brown wrote:
> On Thu, Jul 10, 2014 at 11:36:23PM +0200, Andrew Lunn wrote:
> > Both kirkwood-openrd and kirkwood-t5325 drivers have been replaced
> > with DT based simple-card equivelents. So remove these drivers.
>
> Applied. Please send patches against current code, I needed to hand
> apply this.
Hi Mark
By current do you mean asoc-next? That would not be very easy, since
i'm patching a large number of subsystems here. I don't think the
gpio, or the libata, or the led maintainer would be too happy if i
based the patches on asoc-next! So i picked a plain -rcX kernel,
something neutral to everybody.
Andrew
next prev parent reply other threads:[~2014-07-29 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 21:36 [PATCH v2 00/12] Remove mach-kirkwood Andrew Lunn
2014-07-10 21:36 ` [PATCH v2 03/12] ASoC: kirkwood: Remove unused drivers Andrew Lunn
2014-07-29 19:35 ` Mark Brown
2014-07-29 20:48 ` Andrew Lunn [this message]
2014-07-30 12:11 ` Mark Brown
2014-07-10 21:36 ` [PATCH v2 04/12] ASoC: kirkwood: Remove ARCH_KIRKWOOD dependency Andrew Lunn
2014-07-29 19:35 ` Mark Brown
2014-07-11 14:52 ` [PATCH v2 00/12] Remove mach-kirkwood Tejun Heo
2014-07-13 21:59 ` Jason Cooper
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=20140729204853.GC17763@lunn.ch \
--to=andrew@lunn.ch \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sebastian.hesselbarth@googlemail.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).