From: Felipe Balbi <me@felipebalbi.com>
To: tony@atomide.com
Cc: linux-omap@vger.kernel.org
Subject: [PULL REQUEST] arm omap patches for -next merge window
Date: Wed, 30 Dec 2009 01:01:37 +0200 [thread overview]
Message-ID: <1262127697.28789.92.camel@gandalf> (raw)
After these, all the patches I have for you are
done, besides the CBUS stuff which I want to test
further. DSME is turning off my device right after
boot so I can't really test anything. If you have
some hint, I'd be glad to hear ;-)
The following changes since commit
bb65718ad7ed3c4231f67cf3f8b4a9a071bdfd53:
Felipe Balbi (1):
arm: omap: perseus: kill compile warning on board-perseus2.c
are available in the git repository at:
git://gitorious.org/usb/usb.git for-tony-next
Felipe Balbi (9):
arm: omap: musb: remove unused data
arm: omap: musb: we can use clk framework
arm: omap: musb: remove unused soft_con field
arm: omap: musb: remove unused dma data
arm: omap: musb: remove unnecessary return
arm: omap: gpmc: avoid section definitions on headers
usb: musb: use only clk framework for clk handling
arm: omap: musb: do not pass clock name to driver
arm: omap: musb: get rid of dyn_fifo
arch/arm/mach-omap2/usb-musb.c | 71
+-------------------------------
arch/arm/plat-omap/include/plat/gpmc.h | 2 +-
drivers/usb/musb/musb_core.c | 48 +++++++--------------
drivers/usb/musb/musb_core.h | 2 -
drivers/usb/musb/omap2430.c | 10 +----
drivers/usb/musb/tusb6010.c | 16 +++----
include/linux/usb/musb.h | 4 +-
7 files changed, 28 insertions(+), 125 deletions(-)
--
balbi
next reply other threads:[~2009-12-29 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 23:01 Felipe Balbi [this message]
2009-12-29 23:50 ` [PULL REQUEST] arm omap patches for -next merge window Tony Lindgren
2009-12-30 0:00 ` Felipe Balbi
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=1262127697.28789.92.camel@gandalf \
--to=me@felipebalbi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.