On Tue, Apr 08, 2014 at 05:03:51PM +0100, Borislav Petkov wrote: > On Tue, Apr 08, 2014 at 04:40:17PM +0100, Mark Rutland wrote: > > The patches should be in the same series, but for review purposes it's > > nicer if the bindings are separate patches from the code within that > > series. > > > > I usually look at the drivers implementing bindings and prefer to be > > Cc'd on the whole series, with both the binding and driver. > > Right, but I got only the 3/3 patch on linux-edac which made me wonder. Ah. The whole series should've been Cc'd to linux-edac; I didn't realise that wasn't the case. > So I'm guessing you or someone else would be picking the whole set once > I've acked the EDAC part? Typically the bindings would go with the driver via the appropriate subsystem maintainer. That way we don't get bindings without drivers or vice-versa if there's a problem part-way, and we don't end up with every other driver going via a dt tree. Cheers, Mark. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
