public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: broonie@opensource•wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] Samsung devel for v3.3
Date: Mon, 9 Jan 2012 00:26:41 -0800	[thread overview]
Message-ID: <20120109082640.GI22134@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAOesGMjn5uQEWbxrJryC+jOf=3SYbAnPY4A71NUZKFBi=a0QjA@mail.gmail.com>

On Sun, Jan 08, 2012 at 05:21:02PM -0800, Olof Johansson wrote:

> Mark, Kukjin, can either of you split out the fixes in a separate branch?

Here's some of them, there were a few others I'm aware of that depended
on feature updates.  Ideally we'd actually get all the changes that have
been in -next in.

The following changes since commit 5f0a6e2d503896062f641639dacfe5055c2f593b:

  Linux 3.2-rc7 (2011-12-23 21:51:06 -0800)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git fixes/samsung

Mark Brown (5):
      ARM: SAMSUNG: Fix GPIO space reservation for S3C64xx platforms
      ARM: S3C64XX: Correct reservation of GPIOs for CPU module on Cragganmore
      ARM: SAMSUNG: Guard against multiple inclusion of plat/dma.h
      ARM: SAMSUNG: dma-ops.h needs mach/dma.h
      ARM: SAMSUNG: Declare struct platform_device in plat/s3c64xx-spi.h

 arch/arm/mach-s3c64xx/Kconfig                    |    6 +++---
 arch/arm/mach-s3c64xx/include/mach/crag6410.h    |    3 ++-
 arch/arm/mach-s3c64xx/mach-crag6410.c            |    2 +-
 arch/arm/plat-samsung/Kconfig                    |    8 ++++++++
 arch/arm/plat-samsung/include/plat/dma-ops.h     |    1 +
 arch/arm/plat-samsung/include/plat/dma.h         |    6 +++++-
 arch/arm/plat-samsung/include/plat/s3c64xx-spi.h |    2 ++
 7 files changed, 22 insertions(+), 6 deletions(-)

  parent reply	other threads:[~2012-01-09  8:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 23:33 [GIT PULL] Samsung devel for v3.3 Kukjin Kim
2012-01-06 21:58 ` Olof Johansson
2012-01-07 10:09   ` Kukjin Kim
2012-01-08 20:49   ` Mark Brown
2012-01-09  1:21     ` Olof Johansson
2012-01-09  1:40       ` Kukjin Kim
2012-01-09  2:03         ` Olof Johansson
2012-01-09 15:56         ` Arnd Bergmann
2012-01-09 16:11           ` Mark Brown
2012-01-10  9:06             ` Russell King - ARM Linux
2012-01-10 18:31               ` Mark Brown
2012-01-10 18:44                 ` Nicolas Pitre
2012-01-10 18:46                   ` Mark Brown
2012-01-10 19:00                     ` Nicolas Pitre
2012-01-10 20:13                     ` Arnd Bergmann
2012-01-10 22:37                       ` Mark Brown
2012-01-11  0:11                         ` Olof Johansson
2012-01-11  6:39                           ` Kukjin Kim
2012-01-11 16:19                         ` Arnd Bergmann
2012-01-11 16:50                           ` Olof Johansson
2012-01-11 17:29                             ` Mark Brown
2012-01-11  6:20               ` Kukjin Kim
2012-01-09  8:26       ` Mark Brown [this message]
2012-01-17  6:40         ` Olof Johansson
2012-01-17  7:23           ` Kukjin Kim
2012-01-17  7:24             ` Olof Johansson
2012-01-17 10:53           ` Mark Brown
2012-01-09  9:58     ` Russell King - ARM Linux
2012-01-09 23:24       ` Mark Brown

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=20120109082640.GI22134@opensource.wolfsonmicro.com \
    --to=broonie@opensource$(echo .)wolfsonmicro.com \
    --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