Hi Stephen, Heads up: I just pushed the patch referenced in the below email out to my tree. It will cause a merge conflict, but it shouldn't be too difficult to resolve from what I see in commit 2fd36c552649 "i2c: core: Map OF IRQ at probe time". Let me know if it causes any problems Cheers, g. ---------- Forwarded message ---------- From: Wolfram Sang <wsa@xxxxxxxxxxxxx> Date: Sun, Nov 23, 2014 at 4:22 PM Subject: Re: [PATCH v8 5/8] of: i2c: Export single device registration method To: Grant Likely <grant.likely@xxxxxxxxxxxx> On Fri, Nov 21, 2014 at 01:46:31AM +0000, Grant Likely wrote: > On Tue, 28 Oct 2014 22:36:02 +0200 > , Pantelis Antoniou <pantelis.antoniou@xxxxxxxxxxxx> > wrote: > > Dynamically inserting i2c client device nodes requires the use > > of a single device registration method. Rework and export it. > > > > Signed-off-by: Pantelis Antoniou <pantelis.antoniou@xxxxxxxxxxxx> > > Acked-by: Grant Likely <grant.likely@xxxxxxxxxx> > > Wolfram, this patch and the next one only make sense in conjunction with the overlay > patches, but they don't necessarily need to be merged via the same tree. > I'm happy to take them, but am equally happy to have you take them > (assuming I ack the next patch; I haven't looked at it yet). What is > your preference? OK, now I had the time to look at it, phew. Is this targetted for 3.19? Then you can take it: Reviewed-by: Wolfram Sang <wsa@xxxxxxxxxxxxx> There is a minor conflict caused by this patch in i2c/for-next which should be easy to solve, just remove the irq handling. 2fd36c552649 2014-10-30 15:59 Laurent Pinchart o i2c: core: Map OF IRQ at probe time If you target for later than 3.19, then we need to discuss again, because there might be other i2c core changes coming in.
Attachment:
signature.asc
Description: PGP signature
