public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] regarding PL330 driver for rmk or arm-soc, and slave-dma
Date: Fri, 10 Feb 2012 11:08:00 +0000	[thread overview]
Message-ID: <20120210110800.GU889@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <010601cce7e1$5850a600$08f1f200$%kim@samsung.com>

On Fri, Feb 10, 2012 at 07:47:12PM +0900, Kukjin Kim wrote:
>  arch/arm/common/Kconfig                        |    3 -
>  arch/arm/common/Makefile                       |    1 -
>  arch/arm/common/pl330.c                        | 1959 ------------------------
>  arch/arm/include/asm/hardware/pl330.h          |  338 +++--

I think I've already said this, but I'm going to say it again.

Code in arch/arm/include/asm/hardware/pl330.h which is only used by
drivers/dma/pl330.c, needs to move to drivers/dma/pl330.h or into
drivers/dma/pl330.c itself.

Anything else left over which needs to be used by others can go into
include/linux/amba/pl330.h.

>  arch/arm/mach-exynos/Kconfig                   |    3 +
>  arch/arm/mach-exynos/clock.c                   |    9 +
>  arch/arm/mach-exynos/dma.c                     |  130 ++-
>  arch/arm/mach-exynos/include/mach/irqs.h       |    2 +
>  arch/arm/mach-exynos/include/mach/map.h        |    3 +-
>  arch/arm/plat-samsung/include/plat/dma-pl330.h |   16 +
>  drivers/dma/Kconfig                            |    1 -
>  drivers/dma/pl330.c                            | 1856 ++++++++++++++++++++++
>  12 files changed, 2197 insertions(+), 2124 deletions(-)
>  delete mode 100644 arch/arm/common/pl330.c

  reply	other threads:[~2012-02-10 11:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 10:47 [GIT PULL] regarding PL330 driver for rmk or arm-soc, and slave-dma Kukjin Kim
2012-02-10 11:08 ` Russell King - ARM Linux [this message]
2012-02-10 11:58   ` Kukjin Kim

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=20120210110800.GU889@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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