From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/5] ux500 changes for v3.11
Date: Tue, 4 Jun 2013 14:19:30 +0200 [thread overview]
Message-ID: <CACRpkda7LTeamKWyPVRy1_iOkAvGzb_XZ3sBNPLR_tNerKG4wQ@mail.gmail.com> (raw)
Hi ARM SoC folks,
These are five (5) pull requests for ux500 stuff for v3.11
that I've got queued up. I've done my best to split onto relevant
topic branches, but feel free to merge these any way you like.
1: ux500-core: misc ux500 CPU/SoC changes
2: ux500-clksrc: clocksource changes
3: ux500-pinctrl: pinctrl tables
4: ux500-dma40: DMA40 device tree and refactoring
5: ux500-devicetree: device tree updates
The last two (DMA40 and devicetree) will have a conflict in
arch/arm/mach-ux500/cpu-db8500.c as the DMA40 patch
set removes DMA related platform data.
Typically 4 & 5 are also the larges pull requests so I won't
try to merge them to resolve that conflict, instead I dump
this on you...
Have a look and see what you think. All patches have been
reviewed and ACKed as far as possible and now we need
some linux-next rotation.
I have a sixth branch with defconfig changes but that should
possibly even go in after the merge window. I'm holding it back
for now.
Yours,
Linus Walleij
reply other threads:[~2013-06-04 12:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CACRpkda7LTeamKWyPVRy1_iOkAvGzb_XZ3sBNPLR_tNerKG4wQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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).