From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] omap fixes for v4.6-rc cycle
Date: Fri, 22 Apr 2016 17:21:51 -0700 [thread overview]
Message-ID: <7hmvoltbs0.fsf@baylibre.com> (raw)
In-Reply-To: <20160414203619.GR5973@atomide.com> (Tony Lindgren's message of "Thu, 14 Apr 2016 13:36:19 -0700")
Tony Lindgren <tony@atomide•com> writes:
> The following changes since commit 19e831b272e6db5884be085be66e44da975c73a9:
>
> Merge branch 'fixes-rc2' into omap-for-v4.6/fixes (2016-04-08 09:18:00 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.6/fixes-rc3
>
> for you to fetch changes up to 1560d15861769c23fd981e2d60dc7fd790b21e1e:
>
> ARM: OMAP3: Fix external abort on 36xx waking from off mode idle (2016-04-14 08:27:30 -0700)
>
> ----------------------------------------------------------------
> Fixes for omaps for v4.6-rc cycle:
>
> - Clockdomain fix for dra7 timer interrupts
>
> - Two fixes for GPMC EDMA binding, I missed the need for a merge with
> GPMC changes and EDMA changes
>
> - Fix beagle-x15 eSATA by dropping misconfigured extcon_usb1
>
> - Fix occasional external aborts on 36xx with PM that we've been
> chasing for past few months. It turned out to be duplicate restore
> of INTC registers that can in some cases cause us to hit erratum 1.106.
>
> ----------------------------------------------------------------
Pulled into fixes,
Thanks,
Kevin
next prev parent reply other threads:[~2016-04-23 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 20:36 [GIT PULL] omap fixes for v4.6-rc cycle Tony Lindgren
2016-04-23 0:21 ` Kevin Hilman [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-28 14:50 Tony Lindgren
2016-04-28 15:46 ` Arnd Bergmann
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=7hmvoltbs0.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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