On Tue, Mar 13, 2018 at 02:06:33PM -0700, Tejun Heo wrote: > On Mon, Mar 12, 2018 at 05:10:29PM +0530, Preetham Chandru Ramchandra wrote: > > From: Preetham Ramchandra <pchandru@xxxxxxxxxx> > > > > 1. ADD AHCI support for Tegra210 > > 2. Extend the Tegra AHCI controller device tree binding with Tegra210 > > 3. Update initialization sequence > > 4. Initialize regulators based on chip > > 5. Disable DevSlp > > 6. Disable DIPM > > All look good to me. How should the patches be routed? My suggestion would be that I pick up the arm64 patches (2 and 3) into the Tegra tree and you take the rest (dt-bindings and driver changes) through libata? There are no dependencies between the two sets, other than maybe checkpatch.pl complaining about using an undocumented compatible string until both get merged into v4.17-rc1. I think that's fine, but we can be extra pedantic and carry patch 1 on a stable branch that is merged into both the libata and Tegra trees to avoid that warning. Thierry
Attachment:
signature.asc
Description: PGP signature
