From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Franklin S Cooper Jr <fcooper@ti.com>,
robh+dt@kernel.org, linux@armlinux.org.uk, ssantosh@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] ARM: dts: keystone: Add support for new K2G evm
Date: Wed, 10 May 2017 09:08:50 -0700 [thread overview]
Message-ID: <6e039dc0-7054-66a9-5cee-ce00e0898882@oracle.com> (raw)
In-Reply-To: <20170424202204.24170-1-fcooper@ti.com>
On 4/24/2017 1:22 PM, Franklin S Cooper Jr wrote:
> This patchset adds support for new K2G Industrial Communication Engine
> evm. For now only a bare minimal dts which will allow ram boot. Additional
> peripherals will be added when base K2G SoC patches are upstreamed allowing
> peripherals to be enabled.
>
> Version 2 changes:
> Make various tweaks to allow unit address to be added to memory node.
>
> Franklin S Cooper Jr (4):
> ARM: dts: keystone-k2g: Remove skeleton.dtsi
> ARM: dts: k2g-evm: Add unit address to memory node
> ARM: keystone: Create new binding for K2G ICE evm
> ARM: dts: keystone: Add minimum support for K2G ICE evm
>
Will pick this up for next merge window. Thanks !!
Regards,
Santosh
next prev parent reply other threads:[~2017-05-10 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 20:22 Franklin S Cooper Jr
2017-04-24 20:22 ` [PATCH v2 1/4] ARM: dts: keystone-k2g: Remove skeleton.dtsi Franklin S Cooper Jr
2017-04-24 20:22 ` [PATCH v2 2/4] ARM: dts: k2g-evm: Add unit address to memory node Franklin S Cooper Jr
2017-04-24 20:22 ` [PATCH v2 3/4] ARM: keystone: Create new binding for K2G ICE evm Franklin S Cooper Jr
2017-04-24 20:22 ` [PATCH v2 4/4] ARM: dts: keystone: Add minimum support " Franklin S Cooper Jr
2017-05-05 19:07 ` [PATCH v2 0/4] ARM: dts: keystone: Add support for new K2G evm Franklin S Cooper Jr
2017-05-10 16:08 ` Santosh Shilimkar [this message]
2017-05-22 5:51 ` santosh.shilimkar
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=6e039dc0-7054-66a9-5cee-ce00e0898882@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
/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
all inboxes | Powered by JetHome®