From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject:
Date: Mon, 22 Sep 2014 15:46:12 -0400 [thread overview]
Message-ID: <54207C84.3050103@ti.com> (raw)
In-Reply-To: <1411414879-11551-1-git-send-email-santosh.shilimkar@ti.com>
(Ignore this email... I resent it with $subject line fixed)
On Monday 22 September 2014 03:41 PM, Santosh Shilimkar wrote:
> Subject: [GIT PULL] ARM: dts: Keystone DTS updates for 3.18
>
> Hi Arm-soc folks,
>
> The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
>
> Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/keystone-dts
>
> for you to fetch changes up to b2ed7d98e1c7098f452cf95ab69211a2f8e02ac8:
>
> ARM: dts: keystone: fix bindings for pcie and usb clock nodes (2014-09-22 15:19:36 -0400)
>
> ----------------------------------------------------------------
> Keystone DTS updates for v3.18
>
> - Add IRQ and GPIO nodes
> - Fix SPI chip select
> - Fix usb and pcie clock nodes
>
> ----------------------------------------------------------------
> Grygorii Strashko (2):
> ARM: dts: keystone: add keystone irq controller node
> ARM: dts: keystone: add dsp gpio controllers nodes
>
> Karicheri Muralidharan (1):
> ARM: dts: keystone: k2l: Fix chip selects for SPI devices
>
> Karicheri, Muralidharan (1):
> ARM: dts: keystone: fix bindings for pcie and usb clock nodes
>
> arch/arm/boot/dts/k2e-clocks.dtsi | 6 ++--
> arch/arm/boot/dts/k2e.dtsi | 7 +++++
> arch/arm/boot/dts/k2hk.dtsi | 56 +++++++++++++++++++++++++++++++++++++
> arch/arm/boot/dts/k2l.dtsi | 42 ++++++++++++++++++++++++++++
> arch/arm/boot/dts/keystone.dtsi | 8 ++++++
> 5 files changed, 116 insertions(+), 3 deletions(-)
>
prev parent reply other threads:[~2014-09-22 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 19:41 No subject Santosh Shilimkar
2014-09-22 19:46 ` 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=54207C84.3050103@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.