Hello, On Thu, May 21, 2015 at 03:13:06PM -0700, Brian Norris wrote: > Most subsystems take device tree binding patches for their constituent > drivers. And I see you've been merging others: > > e35b98849f25 ata: sata_rcar: Add r8a7793 device support > 8340bfeb03 ahci: st: Update the ahci_st DT documentation > af64dce4cb3a ahci: st: Provide DT bindings for ST's SATA implementation > a1a205df6ee2 ahci: add support for Hisilicon sata > > All have your sign-off / commit stamp. Yeap, I've been routing some of them. > > Is this > > an exception? > > Not that I know of. Where would you like it to go instead? But the rules have never been clear to me. If the subsystem maintainer is okay with it, I'm happy to take the patches. I'm just kinda curious why this doesn't go through devicetree tree while some other devicetree patches go through there. Can somebody explain the overall policy to me? I'm not looking for some absolute rules and exceptions are fine but I do wanna have a general direction. Thanks. -- tejun -- 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
