From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for v4.0-rc cycle
Date: Sun, 29 Mar 2015 13:59:35 -0700 [thread overview]
Message-ID: <20150329205935.GD13301@localhost> (raw)
In-Reply-To: <20150319204922.GV5140@atomide.com>
On Thu, Mar 19, 2015 at 01:49:23PM -0700, Tony Lindgren wrote:
> The following changes since commit 5b7610f235627878617648a99dd1442997f1c889:
>
> ARM: OMAP2+: Fix wl12xx on dm3730-evm with mainline u-boot (2015-03-06 10:37:34 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/fixes-v4.0-rc4
>
> for you to fetch changes up to 599c376c49323127c9bdbb0fa61a3d4743819bc2:
>
> ARM: dts: Fix gpio interrupts for dm816x (2015-03-18 13:41:34 -0700)
>
> ----------------------------------------------------------------
> Fixes for omaps for the -rc cycle:
>
> - Fix a device tree based booting vs legacy booting regression for
> omap3 crypto hardware by adding the missing DMA channels.
>
> - Fix /sys/bus/soc/devices/soc0/family for am33xx devices.
>
> - Fix two timer issues that can cause hangs if the timer related
> hwmod data is missing like it often initially is for new SoCs.
>
> - Remove pcie hwmods entry from dts as that causes runtime PM to
> fail for the PHYs.
>
> - A paper bag type dts configuration fix for dm816x GPIO
> interrupts that I just noticed. This is most of the changes
> diffstat wise, but as it's a basic feature for connecting
> devices and things work otherwise, it should be fixed.
Merged, thanks.
-Olof
prev parent reply other threads:[~2015-03-29 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 20:49 [GIT PULL] omap fixes for v4.0-rc cycle Tony Lindgren
2015-03-29 20:59 ` Olof Johansson [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=20150329205935.GD13301@localhost \
--to=olof@lixom.net \
--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).