Hi, > > First, I'd like to have this patch squashed with "i2c: nomadik: Add > > Device Tree support to the Nomadik I2C driver". I wanted to do this on > > my own, but the patches do not apply to 3.6-rc5 (with or without > > regulator removal patch from Linus)? > > I'm really not keen on squashing all my patches together. They are > clearly have very different purposes. If you think they are closely > related, then pull them in sequentially, but please don't squash > all my work into a single patch for no other reason than convenience. I can't follow this reasoning. I never asked you to squash all patches, only those two needed to get proper device tree support. Why would you want to let the device being detected via DT and not scan the child nodes immediately? > > I can also take the I2C related changes to the devicetrees via my tree. > > This is not uncommon. Some people prefer to do this via their soc-trees, > > though. I don't care much since this is not really a hard dependency > > causing build failures or merge conflicts, but just needs a little extra > > time until the patches are all there... > > It would be better for all the Device Tree changes go in as a single > patch-set. Again, I don't care where they go, so long as they go in > together. arm-soc seems like the most generic place for them to be > pulled into though. This reasoning I can follow, but how should I know you aimed for that? I only saw a patch [3/3] in one series making the driver probable via DT and a patch [12/19] in another series to scan the child nodes. That's all the infos I got. Some more context would have been helpful. Is there a branch somewhere with all the things collected? Regards, Wolfram -- Pengutronix e.K. | Wolfram Sang | Industrial Linux Solutions | http://www.pengutronix.de/ |
Attachment:
signature.asc
Description: Digital signature
