linux-kernel - Re: [PATCH] mfd: wm5110: Give new AIF2 registers defaults and mark as readable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Nov 2013 08:48:54 +0000
From:	Lee Jones <lee.jones@...aro.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>,
	sameo@...ux.intel.com, patches@...nsource.wolfsonmicro.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mfd: wm5110: Give new AIF2 registers defaults and mark
 as readable

> > 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/