From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
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 15:27:01 +0000 [thread overview]
Message-ID: <20131127152701.GQ3296@lee--X1> (raw)
In-Reply-To: <20131127151639.GX14725@sirena.org.uk>
On Wed, 27 Nov 2013, Mark Brown wrote:
> On Wed, Nov 27, 2013 at 01:24:42PM +0000, Lee Jones wrote:
>
> > 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...
>
> That seems excessive and it probably ought to go in as a bug fix
> afterwards. Given that it's just an addition of data to the table I'd
> expect we could cope, we've routinely done that with similar updates in
> the past without incident.
Ah, is the depends patch in Mainline already? I assumed it was due to
go in during the v3.14 merge window? If it's already in Mainline, then
sure I don't mind if it goes in -fixes via ASoC, no problem.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-11-27 15:27 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
2013-11-27 15:16 ` Mark Brown
2013-11-27 15:27 ` Lee Jones [this message]
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=20131127152701.GQ3296@lee--X1 \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox