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: Thu, 28 Nov 2013 08:48:54 +0000 [thread overview]
Message-ID: <20131128084854.GY3296@lee--X1> (raw)
In-Reply-To: <20131127182841.GF14725@sirena.org.uk>
> > I see. Well I'm not sure how. If we apply it to either ASoC or MFD and
> > other patches pertaining to that file subsequently appear, then
> > conflict is likely. As you know, the commonly used mitigation
>
> It shouldn't be that likely, we're adding entries to the middle of big,
> ordered tables - conflicts would be caused by something like changing
> or adding adjacent entries and they're pretty trivial to resolve. It's
> not like a restructring of the code or anything.
>
> > technique we usually employ is immutable branches, but this was not
> > employed in this case for one reason or another. So if we apply it now
> > to either one of the trees we will be hedging our bets.
>
> Hedging our bets would be applying it to both trees!
Well I'm sure we'd sort out any conflicts.
Go ahead and apply it to your tree with my Ack then.
In future, let's do the immutable branch thing, it's worked well thus
far.
--
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-28 8:49 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
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 [this message]
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=20131128084854.GY3296@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 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.