public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: stigge@antcom•de (Roland Stigge)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: LPC32xx: DTS updates #2
Date: Tue, 25 Sep 2012 10:25:08 +0200	[thread overview]
Message-ID: <50616A64.8040600@antcom.de> (raw)

Hi Arnd and Olof,

this is a second round of mach-lpc32xx specific updates for 3.7, below
the dts branch. Only one patch for adjusting phy3250.dts.

Thanks,

Roland


The following changes since commit 25b3ab6c7e39e42245d98c27d25d9902baec7b65:

  ARM: LPC32xx: Extend dts for EA3250 board (2012-09-06 11:40:48 +0200)

are available in the git repository at:

  git://git.antcom.de/linux-2.6.git lpc32xx/dts

for you to fetch changes up to 07c7e12ca7e32e942d2c42dd67329c5fc3886b07:

  ARM: LPC32xx: LED fix in PHY3250 DTS file (2012-09-25 10:11:41 +0200)

----------------------------------------------------------------
Roland Stigge (1):
      ARM: LPC32xx: LED fix in PHY3250 DTS file

 arch/arm/boot/dts/phy3250.dts |   12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

             reply	other threads:[~2012-09-25  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  8:25 Roland Stigge [this message]
2012-09-29 21:27 ` [GIT PULL] ARM: LPC32xx: DTS updates #2 Olof Johansson

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=50616A64.8040600@antcom.de \
    --to=stigge@antcom$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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