From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Vignesh R <vigneshr@ti.com>, Santosh Shilimkar <ssantosh@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] 66AK2G: Add DT nodes for few peripherals
Date: Sat, 2 Dec 2017 20:01:40 -0800 [thread overview]
Message-ID: <9a1a50a9-d77e-44fb-be47-32fb8d4735f2@oracle.com> (raw)
In-Reply-To: <20171123075154.3938-1-vigneshr@ti.com>
On 11/22/17 11:51 PM, Vignesh R wrote:
> This patch series adds DT nodes for bunch of peripherials on 66AK2G EVM and
> 66AK2G ICE boards.
>
> Tested on 66AK2G EVM and ICE boards
>
>
> Vignesh R (6):
> ARM: dts: keystone-k2g: Add QSPI DT entry
> ARM: dts: keystone-k2g-evm: Fix botched up merge
> ARM: dts: keystone-k2g: Move ti,non-removable property to board dts
> ARM: dts: keystone-k2g-evm: Add QSPI DT node.
> ARM: dts: keystone-k2g-ice: Add DT nodes for few peripherals
> ARM: configs: keystone_defconfig: Enable few peripheral drivers
>
Series applied. Please submit the follow up patch for
multi-v7 config.
Regards,
Santosh
prev parent reply other threads:[~2017-12-03 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 7:51 [PATCH 0/6] 66AK2G: Add DT nodes for few peripherals Vignesh R
2017-11-23 7:51 ` [PATCH 1/6] ARM: dts: keystone-k2g: Add QSPI DT entry Vignesh R
2017-11-23 7:51 ` [PATCH 2/6] ARM: dts: keystone-k2g-evm: Fix botched up merge Vignesh R
2017-11-23 7:51 ` [PATCH 3/6] ARM: dts: keystone-k2g: Move ti,non-removable property to board dts Vignesh R
2017-11-23 7:51 ` [PATCH 4/6] ARM: dts: keystone-k2g-evm: Add QSPI DT node Vignesh R
2017-11-23 7:51 ` [PATCH 5/6] ARM: dts: keystone-k2g-ice: Add DT nodes for few peripherals Vignesh R
2017-11-23 7:51 ` [PATCH 6/6] ARM: configs: keystone_defconfig: Enable few peripheral drivers Vignesh R
2017-12-03 4:00 ` santosh.shilimkar
2017-12-04 9:00 ` Vignesh R
2017-12-04 17:36 ` Santosh Shilimkar
2017-12-03 4:01 ` santosh.shilimkar [this message]
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=9a1a50a9-d77e-44fb-be47-32fb8d4735f2@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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).