From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, tony@atomide.com
Subject: [RFC 0/2] ARM: OMAP: dma.h cleanup
Date: Wed, 13 Mar 2013 22:15:47 +0200 [thread overview]
Message-ID: <1363205749-9905-1-git-send-email-jarkko.nikula@bitmer.com> (raw)
I don't know is this good or bad idea, thus RFC.
I got this idea after noticing that McBSP DMA channel definitions are no
longer used for OMAP2 and EAC DMA channel were never used in upstream.
Scripts here are used to remove all of those unused ones.
Build tested with omap1_defconfig and omap2plus_defconfig.
--
Jarkko
next reply other threads:[~2013-03-13 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 20:15 Jarkko Nikula [this message]
2013-03-13 20:15 ` [RFC 1/2] ARM: OMAP1: Remove unused DMA channel definitions Jarkko Nikula
2013-03-13 20:15 ` [RFC 2/2] ARM: OMAP2+: " Jarkko Nikula
2013-03-20 16:42 ` [RFC 0/2] ARM: OMAP: dma.h cleanup Tony Lindgren
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=1363205749-9905-1-git-send-email-jarkko.nikula@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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).