From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/7] omap dma clean-up for v3.11 merge window
Date: Tue, 18 Jun 2013 11:07:26 -0700 [thread overview]
Message-ID: <mailman.9.1371578947.1060.linux-arm-kernel@lists.infradead.org> (raw)
In-Reply-To: <pull-1371578847-800598>
The following changes since commit 7d132055814ef17a6c7b69f342244c410a5e000f:
Linux 3.10-rc6 (2013-06-15 11:51:07 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.11/dma-signed
for you to fetch changes up to e2081f96ba1be3aa22a44daec82af9b226a6d7d6:
ARM: OMAP1: Remove dma.h (2013-06-18 00:12:34 -0700)
----------------------------------------------------------------
Non-critical omap DMA fixes and removal of unused legacy code.
----------------------------------------------------------------
Jarkko Nikula (8):
ARM: OMAP2+: Remove AES crypto device DMA channel definitions
ARM: OMAP2+: Remove duplicated DMA channel definitions
ARM: OMAP2+: hwmod: Remove remaining DMA channel definitions
ARM: OMAP2+: Remove dma.h
ARM: OMAP1: Remove McBSP DMA channel definitions
ARM: OMAP1: Remove duplicated DMA channel definitions
ARM: OMAP1: Remove legacy irda.h and irda setup from board files
ARM: OMAP1: Remove dma.h
R Sricharan (2):
ARM: OMAP: dma: Remove the wrong dev_id check
ARM: OMAP: dma: Fix the dma_chan_link_map init order
Rajendra Nayak (1):
ARM: OMAP: dma: Remove the erroneous freeing of platform data
arch/arm/mach-omap1/board-h2.c | 36 -------------
arch/arm/mach-omap1/board-palmte.c | 31 -----------
arch/arm/mach-omap1/board-palmtt.c | 30 -----------
arch/arm/mach-omap1/board-palmz71.c | 31 -----------
arch/arm/mach-omap1/board-sx1.c | 36 -------------
arch/arm/mach-omap1/devices.c | 9 ++--
arch/arm/mach-omap1/dma.c | 2 -
arch/arm/mach-omap1/dma.h | 42 ---------------
arch/arm/mach-omap1/include/mach/irda.h | 33 ------------
arch/arm/mach-omap1/lcd_dma.c | 2 -
arch/arm/mach-omap1/mcbsp.c | 33 ++++++------
arch/arm/mach-omap2/devices.c | 1 -
arch/arm/mach-omap2/dma.h | 61 ----------------------
.../mach-omap2/omap_hwmod_2xxx_3xxx_ipblock_data.c | 21 ++++----
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 19 ++++---
arch/arm/plat-omap/dma.c | 11 ++--
16 files changed, 43 insertions(+), 355 deletions(-)
delete mode 100644 arch/arm/mach-omap1/dma.h
delete mode 100644 arch/arm/mach-omap1/include/mach/irda.h
delete mode 100644 arch/arm/mach-omap2/dma.h
next prev parent reply other threads:[~2013-06-18 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 18:07 [GIT PULL 1/7] omap soc fixes for v3.11 merge window Tony Lindgren
2013-06-18 18:07 ` [GIT PULL 3/7] omap voltdomain clean-up " Tony Lindgren
2013-06-18 18:07 ` [GIT PULL 2/7] omap serial pm cleanup " Tony Lindgren
2013-06-18 18:07 ` Tony Lindgren [this message]
2013-06-18 18:07 ` [GIT PULL 5/7] omap board changes " Tony Lindgren
2013-06-18 18:07 ` [GIT PULL 6/7] omap gpmc reworked suspend patch " Tony Lindgren
2013-06-18 18:07 ` [GIT PULL 7/7] omap mailbox move to drivers " Tony Lindgren
2013-06-20 14:55 ` [GIT PULL 1/7] omap soc fixes " Arnd Bergmann
[not found] <0LmtTQ-1UNOje0BA4-00hdOq@mx.kundenserver.de>
2013-06-20 14:56 ` [GIT PULL 4/7] omap dma clean-up " 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=mailman.9.1371578947.1060.linux-arm-kernel@lists.infradead.org \
--to=tony@atomide.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).