public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: soc for 4.4 #1
Date: Thu, 1 Oct 2015 14:33:39 +0200	[thread overview]
Message-ID: <1443702819-32032-1-git-send-email-nicolas.ferre@atmel.com> (raw)

Arnd, Olof, Kevin,

This is our first SoC batch for 4.4 and it's quite little.
Some content may come later but we still have to figure out if it goes through
arm-soc or the clock tree by Mike.

Thanks, best regards,

The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:

  Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git tags/at91-soc

for you to fetch changes up to 6f112a08c1ed717a015dae190e289d53085c1bc4:

  ARM: at91: debug: use DEBUG_UART_PHYS (2015-09-21 16:31:15 +0200)

----------------------------------------------------------------
First little batch of SoC changes for 4.4:
- a MAINTAINER addition to cover SAMA5 SoCs
- removal of one unneeded header file
- for low-level serial output, use the DEBUG_UART_PHYS

----------------------------------------------------------------
Alexandre Belloni (3):
      MAINTAINERS: explicitly add Atmel SAMA5
      ARM: at91: remove useless includes in platform_data/atmel.h
      ARM: at91: debug: use DEBUG_UART_PHYS

 MAINTAINERS                         |  2 +-
 arch/arm/Kconfig.debug              | 41 ++++++++++++++---------------------
 arch/arm/include/debug/at91.S       | 18 ++++-----------
 include/linux/platform_data/atmel.h |  8 -------
 4 files changed, 21 insertions(+), 48 deletions(-)

-- 
Nicolas Ferre

             reply	other threads:[~2015-10-01 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 12:33 Nicolas Ferre [this message]
2015-10-06 14:44 ` [GIT PULL] at91: soc for 4.4 #1 Arnd Bergmann

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=1443702819-32032-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