From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] omap soc changes for v4.3
Date: Mon, 27 Jul 2015 14:47:38 +0200 [thread overview]
Message-ID: <20150727124738.GI14224@localhost> (raw)
In-Reply-To: <55b22a40.4b226b0a.bc37c.ffffce3aSMTPIN_ADDED_BROKEN@mx.google.com>
On Fri, Jul 24, 2015 at 05:06:10AM -0700, Tony Lindgren wrote:
> The following changes since commit bc0195aad0daa2ad5b0d76cce22b167bc3435590:
>
> Linux 4.2-rc2 (2015-07-12 15:10:30 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.3/soc-signed
>
> for you to fetch changes up to 24da741c678f865de3182194604dbddcc7fc7f3c:
>
> Merge branch 'dm814x-soc' into omap-for-v4.3/soc (2015-07-23 21:59:18 -0700)
>
> ----------------------------------------------------------------
> SoC changes for omaps for v4.3 merge window:
>
> - Clean-up omap4_local_timer_init to drop deal legacy code
>
> - Provide proper IO map table for dra7
>
> - Clean-up IOMMU layer init code as it now uses IOMMU framework
>
> - A series of changes to fix up dm814x support that's been in a broken
> half-merged state for quite some time
>
> - A series of PRCM and hwmod changes via Paul Walmsley <paul@pwsan.com>:
>
> - I/O wakeup support for AM43xx
> - register lock and unlock support to the hwmod code (needed for the RTC
> IP blocks on some chips)
> - several fixes for sparse warnings and an unnecessary null pointer test
> - a DRA7xx clockdomain configuration workaround, to deal with some hardware
> bugs
Merged, thanks!
-Olof
next parent reply other threads:[~2015-07-27 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55b22a40.4b226b0a.bc37c.ffffce3aSMTPIN_ADDED_BROKEN@mx.google.com>
2015-07-27 12:47 ` Olof Johansson [this message]
2015-07-24 12:06 [GIT PULL 1/2] omap soc changes for v4.3 Tony Lindgren
2015-07-24 12:08 ` Tony Lindgren
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=20150727124738.GI14224@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).