Stefan Wahren <stefan.wahren@xxxxxxxx> writes: > Hi Baruch, > > Am 16.01.2018 um 11:49 schrieb Baruch Siach: >> Hi Linus, >> >> On Tue, Jan 16, 2018 at 10:57:32AM +0100, Linus Walleij wrote: >>> On Sat, Jan 13, 2018 at 10:57 AM, Stefan Wahren <stefan.wahren@xxxxxxxx> wrote: >>>>> Baruch Siach <baruch@xxxxxxxxxx> hat am 11. Januar 2018 um 20:44 geschrieben: >>>>> >>>>> Add latest firmware property tags from the latest Raspberry Pi downstream >>>>> kernel. This is needed for the GPIO tags, so we can control the GPIO >>>>> multiplexor lines. >>>>> >>>>> Signed-off-by: Baruch Siach <baruch@xxxxxxxxxx> >>>> Acked-by: Stefan Wahren <stefan.wahren@xxxxxxxx> >>>> >>>> Maybe this is obvious, but patch #3 depends on this change so no cherry-picking allowed. >>> I will save this for after the merge window as it feels now. >>> >>> But as far as I have the right ACKs I can put it in the GPIO tree. >>> >>> Baruch: can you resend the series with all ACKs and push me >>> to apply it all in the GPIO tree if you're fine with this approach? >> I plan to send another revision of this series later today to address Stefan's >> comments on this one. Once Stefan and/or Eric ack the entire series, I'm fine >> with you taking it through the GPIO tree if it is OK with the BCM2835 >> maintainers. >> >> baruch >> > > we also need an ACK from the devicetree maintainers. So please send a > copy of the binding patch V3 to Rob Herring and Marc Rutland. I'll be happy to see patch 1-3 go through the GPIO tree, and we'd take #4 in the 2835 tree. The only risk I see is if we need patch 1 for some other change in this cycle -- seems unlikely, but if Linus applied the series starting from a rc1 tag and merged it in, then we'll also be able to merge that patch over to any other branch we need without duplicating it in git history. Once you get this resent with the DT folks Cced, hopefully it'll be pretty quick.
Attachment:
signature.asc
Description: PGP signature
