linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: lee.jones@linaro.org, linus.walleij@linaro.org, gnurou@gmail.com,
	lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.de,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
	ckeepax@opensource.wolfsonmicro.com
Subject: Re: [PATCH 3/3] ASoC: arizona: Add initial CS47L24 codec driver
Date: Tue, 18 Nov 2014 17:34:32 +0000	[thread overview]
Message-ID: <20141118173432.GA28674@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20141118145114.GN22111@sirena.org.uk>

On Tue, Nov 18, 2014 at 02:51:14PM +0000, Mark Brown wrote:
> On Tue, Nov 11, 2014 at 05:05:43PM +0000, Richard Fitzgerald wrote:
> > Signed-off-by: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
> > ---
> >  sound/soc/codecs/Kconfig   |    8 +
> >  sound/soc/codecs/Makefile  |    2 +
> >  sound/soc/codecs/arizona.c |    5 +
> >  sound/soc/codecs/cs47l24.c | 1133 ++++++++++++++++++++++++++++++++++++++++++++
> >  sound/soc/codecs/cs47l24.h |   23 +
> 
> Can you split out the arizona.c change into a separate patch to be
> merged via the MFD tree along with the new #define please?  Everything
> else can go in via the ASoC tree but that build depends on the new
> defines.

Will do. I'll wait until we've agreed what to do with the MFD tables
and then respin all these patches.

It's probably worth merging the set of WM8280/WM8281 support patches
first as they are simpler. Then I can rebase these CS47L24 patches
on top of that.


  reply	other threads:[~2014-11-18 17:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 16:52 [PATCH 0/3] Driver for Cirrus Logic CS47L24 codec Richard Fitzgerald
2014-11-11 17:03 ` [PATCH 1/3] mfd: arizona: Add support for CS47L24 Richard Fitzgerald
2014-11-12  9:34   ` Charles Keepax
2014-11-11 17:04 ` [PATCH 2/3] gpio: " Richard Fitzgerald
2014-11-11 17:16   ` Mark Brown
2014-11-17  6:41   ` Linus Walleij
2014-11-17  9:58     ` Richard Fitzgerald
2014-11-17 15:03       ` Mark Brown
2014-11-11 17:05 ` [PATCH 3/3] ASoC: arizona: Add initial CS47L24 codec driver Richard Fitzgerald
2014-11-18 14:51   ` Mark Brown
2014-11-18 17:34     ` Richard Fitzgerald [this message]
2014-11-11 17:15 ` [PATCH 1/3] mfd: arizona: Add support for CS47L24 Richard Fitzgerald
2014-11-13 10:12   ` Lee Jones
2014-11-13 16:24     ` Richard Fitzgerald
2014-11-13 16:40     ` Charles Keepax
2014-11-17 12:16       ` Lee Jones
2014-11-17 12:54         ` Richard Fitzgerald
2014-11-17 15:01           ` Mark Brown
2014-11-18 11:34             ` Lee Jones
2014-11-18 13:10               ` Richard Fitzgerald
2014-11-17 15:13           ` Charles Keepax
2014-11-18 15:00             ` Mark Brown
2014-11-19 16:51   ` Lee Jones

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=20141118173432.GA28674@opensource.wolfsonmicro.com \
    --to=rf@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=gnurou@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=perex@perex.cz \
    --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).