From: Thierry Reding <thierry.reding@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Preetham Chandru Ramchandra <pchandru@nvidia.com>,
cyndis@kapsi.fi, robh+dt@kernel.org, mark.rutland@arm.com,
preetham260@gmail.com, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-ide@vger.kernel.org,
vbyravarasu@nvidia.com, pkunapuli@nvidia.com
Subject: Re: [PATCH V8 0/9] Refactor and add AHCI support for Tegra210
Date: Tue, 13 Mar 2018 23:42:59 +0100 [thread overview]
Message-ID: <20180313224258.GA23414@mithrandir> (raw)
In-Reply-To: <20180313210633.GP2943022@devbig577.frc2.facebook.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
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@nvidia.com>
> >
> > 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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-13 22:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 11:40 [PATCH V8 0/9] Refactor and add AHCI support for Tegra210 Preetham Chandru Ramchandra
2018-03-12 11:40 ` [PATCH V8 1/9] dt-bindings: Tegra210: add binding documentation Preetham Chandru Ramchandra
2018-03-12 12:14 ` Thierry Reding
2018-03-18 12:49 ` Rob Herring
2018-03-12 11:40 ` [PATCH V8 2/9] arm64: tegra: Add SATA node for Tegra210 Preetham Chandru Ramchandra
2018-03-12 11:40 ` [PATCH V8 3/9] arm64: tegra: Enable AHCI on Jetson TX1 Preetham Chandru Ramchandra
2018-03-12 11:40 ` [PATCH V8 4/9] ata: ahci_tegra: Update initialization sequence Preetham Chandru Ramchandra
2018-03-12 12:14 ` Thierry Reding
2018-03-12 11:40 ` [PATCH V8 5/9] ata: ahci_tegra: initialize regulators from soc struct Preetham Chandru Ramchandra
2018-03-12 12:14 ` Thierry Reding
2018-03-12 11:40 ` [PATCH V8 6/9] ata: ahci_tegra: disable devslp for Tegra124 Preetham Chandru Ramchandra
2018-03-12 12:15 ` Thierry Reding
2018-03-12 11:40 ` [PATCH V8 7/9] ata: ahci_tegra: disable DIPM Preetham Chandru Ramchandra
2018-03-12 12:15 ` Thierry Reding
2018-03-12 11:40 ` [PATCH V8 8/9] ata: ahci_tegra: Add AHCI support for Tegra210 Preetham Chandru Ramchandra
2018-03-12 12:15 ` Thierry Reding
2018-03-12 11:40 ` [PATCH V8 9/9] ata: change Tegra124 to Tegra Preetham Chandru Ramchandra
2018-03-12 12:15 ` Thierry Reding
2018-03-13 21:06 ` [PATCH V8 0/9] Refactor and add AHCI support for Tegra210 Tejun Heo
2018-03-13 22:42 ` Thierry Reding [this message]
2018-03-14 15:25 ` Tejun Heo
2018-03-14 16:38 ` Thierry Reding
2018-03-14 9:50 ` Thierry Reding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180313224258.GA23414@mithrandir \
--to=thierry.reding@gmail.com \
--cc=cyndis@kapsi.fi \
--cc=devicetree@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pchandru@nvidia.com \
--cc=pkunapuli@nvidia.com \
--cc=preetham260@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tj@kernel.org \
--cc=vbyravarasu@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).