From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: broonie@kernel.org, sameo@linux.intel.com,
patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: wm5110: Give new AIF2 registers defaults and mark as readable
Date: Wed, 27 Nov 2013 14:19:18 +0000 [thread overview]
Message-ID: <20131127141918.GA10013@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20131127132442.GJ3296@lee--X1>
On Wed, Nov 27, 2013 at 01:24:42PM +0000, Lee Jones wrote:
> > The registers associated with the new channels on AIF2 were accidentally
> > missing defaults and not marked as readable this patch fixes this.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> > ---
> >
> > This patch depends on the patch:
> >
> > "ASoC: wm5110: Add extra AIF2 channels"
> >
> > Which is going through the ASoC tree at the moment, so
> > probably best to send this patch through the ASoC tree as
> > well. As such I have generated it against Mark's for-next
> > branch, let me know if it needs regenerating.
>
> Hmm... this is awkward!
>
> I'm not keen on this patch going through ASoC, as it might make things
> equally as awkward later in the cycle. We should have created an
> immutable branch for that really. I guess this will have to wait for
> the next cycle now...
To be honest there is no urgent rush to get this in so it can
wait until the next cycle, I will just have to make sure I
remember to resend.
Thanks,
Charles
next prev parent reply other threads:[~2013-11-27 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 12:51 [PATCH] mfd: wm5110: Give new AIF2 registers defaults and mark as readable Charles Keepax
2013-11-27 13:24 ` Lee Jones
2013-11-27 14:19 ` Charles Keepax [this message]
2013-11-27 15:16 ` Mark Brown
2013-11-27 15:27 ` Lee Jones
2013-11-27 16:07 ` Mark Brown
2013-11-27 16:42 ` Lee Jones
2013-11-27 18:28 ` Mark Brown
2013-11-28 8:48 ` Lee Jones
2013-11-28 10:35 ` 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=20131127141918.GA10013@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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 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.