From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap dts changes for v4.4 merge window, part 2
Date: Fri, 23 Oct 2015 22:19:25 +0200 [thread overview]
Message-ID: <4174355.uUodgcne1B@wuerfel> (raw)
In-Reply-To: <20151020193501.GN3078@atomide.com>
On Tuesday 20 October 2015 12:35:02 Tony Lindgren wrote:
> Few more omap dts changes for v4.4 merge window, mostly to fix and clean
> up some omap5 issues to allow adding other omap5 boards. Also some other
> fixes and clean-up:
>
> - Fix SDIO WLAN for omap5 that's been broken for a while. As further
> patches are still needed for wl18xx, no need for stable on this one.
>
> - Move most of omap5 support into omap5-board-common.dtsi as most omap5
> boards seem to share the same basic set of devices.
>
> - Add minimal IGEPv5 support using based on omap5-board-common.dtsi
>
> - Remove now unneedes gpio hogging for dra72-evm
>
> - Update Javier Martinez Canillas email address
>
> - Change earlier IGEP boards to use IOPAD pinmux macros
>
Pulled into next/dt, thanks!
Arnd
prev parent reply other threads:[~2015-10-23 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 19:35 [GIT PULL] omap dts changes for v4.4 merge window, part 2 Tony Lindgren
2015-10-23 20:19 ` Arnd Bergmann [this message]
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=4174355.uUodgcne1B@wuerfel \
--to=arnd@arndb.de \
--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