From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND Patch 0/9] dts pending patches for TI omap
Date: Wed, 5 Mar 2014 11:50:53 -0800 [thread overview]
Message-ID: <20140305195053.GG7599@atomide.com> (raw)
In-Reply-To: <1393858226-32595-1-git-send-email-mugunthanvnm@ti.com>
* Mugunthan V N <mugunthanvnm@ti.com> [140303 06:53]:
> Benoit/Tony
>
> Here I am send all the pending dt patches that can go into 3.15 merge window,
> all the patches were already posted to mailing list and has beed reviewed.
>
> I have rebased the patches on top of
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git omap-for-v3.15/dt
> and fixed all the merge conflicts.
>
> Pasting the mail archive for the patches series
>
> * Add ABB device nodes
> http://linux-kernel.2935.n7.nabble.com/PATCH-0-4-ARM-dts-OMAP3630-Add-ABB-device-nodes-td794852.html
>
> * MMC hot plug support
> http://mail.blameitonlove.com/lists/linux-omap/msg101933.html
> Dropped [PATCH 2/3] ARM: dts: am335x-evmsk: add SD card hotplug support as this
> is already merged with commit id 29ea5efb0bb612d352aa360de26e2095cb230e4a
>
> * DRA7 Cross bar DTS patches
> Cross bar driver has been pulled for next merge, so the dts patches can also
> be pulled for next merge window.
>
> Here is the pull request for the same patch series.
>
> The following changes since commit f777ba1780584b100ab9664cc06d04f3bb273a84:
>
> Merge tag 'for_3.15/dts_signed' of git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt into omap-for-v3.15/dt (2014-03-02 14:22:03 -0800)
>
> are available in the git repository at:
>
>
> git://git.ti.com/~mugunthanvnm/ti-linux-kernel/linux.git omapdt-for-3.15
>
> for you to fetch changes up to 5f78b45aa45c5b2c4de895c3b0740fda4684dae4:
>
> ARM: DTS: DRA7: Add routable-irqs property for gic node (2014-03-03 19:53:25 +0530)
Thanks applying all except for the crossbar ones into
omap-for-v3.15/dt.
Please resend the last three patches once the dependencies
are merged to mainline kernel as otherwise the interrupt
nubers are all wrong without the crossbar driver related
code.
Regards,
Tony
next prev parent reply other threads:[~2014-03-05 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 14:50 [RESEND Patch 0/9] dts pending patches for TI omap Mugunthan V N
2014-03-03 14:50 ` Mugunthan V N
2014-03-03 14:50 ` [RESEND Patch 1/9] ARM: dts: am437x gp-evm: add sd card dt nodes Mugunthan V N
2014-03-03 14:50 ` [RESEND Patch 2/9] ARM: dts: am335x-evm: add SD card hotplug support Mugunthan V N
2014-03-03 14:50 ` [RESEND Patch 3/9] ARM: dts: am43x-epos-evm: " Mugunthan V N
2014-03-03 14:50 ` [RESEND Patch 4/9] ARM: dts: OMAP36xx: Add device node for ABB Mugunthan V N
2014-03-03 14:50 ` [RESEND Patch 5/9] ARM: dts: OMAP4: Add device nodes " Mugunthan V N
2014-03-03 14:50 ` [RESEND Patch 6/9] ARM: dts: DRA7: " Mugunthan V N
2014-03-03 14:50 ` [RESEND Patch 7/9] ARM: DTS: DRA7: Add crossbar device binding Mugunthan V N
2014-03-03 14:50 ` [RESEND Patch 8/9] ARM: DTS: DRA7: Replace peripheral interrupt numbers with crossbar inputs Mugunthan V N
2014-03-03 14:50 ` [RESEND Patch 9/9] ARM: DTS: DRA7: Add routable-irqs property for gic node Mugunthan V N
2014-03-05 19:50 ` Tony Lindgren [this message]
2014-03-06 4:33 ` [RESEND Patch 0/9] dts pending patches for TI omap Sricharan R
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=20140305195053.GG7599@atomide.com \
--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).