linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: fixes for 3.11 #1
Date: Wed, 14 Aug 2013 10:33:33 +0200	[thread overview]
Message-ID: <1376469213-30981-1-git-send-email-nicolas.ferre@atmel.com> (raw)

Arnd, Olof, Kevin,

This is the first (late) fixes pull-reqest for AT91. I would understand if
you refuse it because we are already at -rc5 ;-) ...

On the other hand, the line count is very low and all patches are pretty
obvious.

Thanks, best regards,

The following changes since commit ad81f0545ef01ea651886dddac4bef6cec930092:

  Linux 3.11-rc1 (2013-07-14 15:18:27 -0700)

are available in the git repository at:

  git://github.com/at91linux/linux-at91.git tags/at91-fixes

for you to fetch changes up to a57603ca2871ee0773b00839c1ea35c4a2d3eeb0:

  ARM: at91/DT: fix at91sam9n12ek memory node (2013-08-14 09:56:31 +0200)

----------------------------------------------------------------
Device tree related fixes:
- USB host numbering for 9x5 which was preventing from using all ports
- a missing UART (not USART) clock lookup table was preventing from using
  them on 9x5
- too large amount of memory was specified for 9n12ek

----------------------------------------------------------------
Boris BREZILLON (1):
      ARM: at91: add missing uart clocks DT entries

Nicolas Ferre (2):
      ARM: at91/DT: at91sam9x5ek: fix USB host property to enable port C
      ARM: at91/DT: fix at91sam9n12ek memory node

 arch/arm/boot/dts/at91sam9n12ek.dts | 4 ++--
 arch/arm/boot/dts/at91sam9x5ek.dtsi | 5 +++--
 arch/arm/mach-at91/at91sam9x5.c     | 2 ++
 3 files changed, 7 insertions(+), 4 deletions(-)

-- 
Nicolas Ferre

             reply	other threads:[~2013-08-14  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14  8:33 Nicolas Ferre [this message]
2013-08-16  5:53 ` [GIT PULL] at91: fixes for 3.11 #1 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=1376469213-30981-1-git-send-email-nicolas.ferre@atmel.com \
    --to=nicolas.ferre@atmel.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 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).