From: Nishanth Menon <nm@ti.com>
To: Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>, <tony@atomide.com>
Cc: Tony Lindgren <tony@atomide.com>,
Russell King <linux@armlinux.org.uk>,
Santosh Shilimkar <ssantosh@kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <t-kristo@ti.com>, Sekhar Nori <nsekhar@ti.com>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Sudeep Holla <sudeep.holla@arm.com>, <arm@kernel.org>
Subject: Re: [PATCH V2 0/5] arm64: Initial support Texas Instrument's AM654 Platform
Date: Wed, 18 Jul 2018 13:04:55 -0500 [thread overview]
Message-ID: <20180718180455.gaej4fgf47zytdxk@kahuna> (raw)
In-Reply-To: <20180626162615.19194-1-nm@ti.com>
On 16:26-20180626, Nishanth Menon wrote:
> Hi,
>
> This is an minor update from V1 posted earlier:
> https://marc.info/?l=linux-kernel&m=152943745424138&w=2
>
> The following series enables support for newest addition in TI's SoC
> portfolio - AM654 SoC.
>
> The series is based off v4.18-rc1, also available here:
> https://github.com/nmenon/linux-2.6-playground/tree/upstream/v4.18-rc1/k3-1-am6-base
>
> Key changes since RFC are indicated in respective patches:
> * Pickedup Tony's Reviewed by
> * Modified cbass nodes to indicate interconnect (patch #3 in the series)
Hi Tony,
Apologies on the off-request. Looks like Tero might be on vacation
and might not be able to send the Pull request to arm-soc folks on time.
Requesting you to pick them up on our behalf for v4.19 if it that is
fine with you. We do have Rob's ack on the bindings themselves, and
the patches also have been reviewed as well.
Patchwork links:
https://patchwork.kernel.org/patch/10527309/
https://patchwork.kernel.org/patch/10489509/
https://patchwork.kernel.org/patch/10489547/
https://patchwork.kernel.org/patch/10489543/
https://patchwork.kernel.org/patch/10489513/
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2018-07-18 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 16:26 [PATCH V2 0/5] arm64: Initial support Texas Instrument's AM654 Platform Nishanth Menon
2018-06-26 16:26 ` [PATCH V2 1/5] dt-bindings: arm: ti: Add bindings for AM654 SoC Nishanth Menon
2018-07-03 22:15 ` Rob Herring
2018-06-26 16:26 ` [PATCH V2 2/5] arm64: Add support for TI's K3 Multicore SoC architecture Nishanth Menon
2018-06-26 16:26 ` [PATCH V2 3/5] arm64: dts: ti: Add Support for AM654 SoC Nishanth Menon
2018-06-26 16:26 ` [PATCH V2 4/5] soc: ti: Add Support for AM654 SoC config option Nishanth Menon
2018-06-26 16:26 ` [PATCH V2 5/5] arm64: dts: ti: Add support for AM654 EVM base board Nishanth Menon
2018-07-18 18:04 ` Nishanth Menon [this message]
2018-07-18 18:57 ` [PATCH V2 0/5] arm64: Initial support Texas Instrument's AM654 Platform Tony Lindgren
2018-07-18 22:38 ` Nishanth Menon
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=20180718180455.gaej4fgf47zytdxk@kahuna \
--to=nm@ti.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
--cc=will.deacon@arm.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).