> >>>>I have just sent single patch, which has dependency on regulator > >>>>changes. Please review, ack and queue up. > >>> > >>>A little presumptuous, don't you think? ;) > >>> > >>>>[PATCH-v3] mfd: 88pm80x: Add 88pm860 chip type support > >>>>https://patchwork.kernel.org/patch/6826531/ > >>> > >>>So nothing depends on this anymore, right? > >>> > >> > >>No, regulato patch depends on this. > >>Mark needs your tag in order to take above patch through regulator tree. > > > >That's not how we usually do things. > > > >However, as this patch is a very simple one, it shouldn't cause too > >many issues if it were to go in via the Regulator tree. > > > > Thanks for your ack. > > And I understand your concern, but not sure how would you solve such > dependency?
We usually share immutable branches, which contain all of the patches in the correct order. > Another point which keeps bugging me is, git-bisect. ... which also mitigates bisect issues. -- 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/