From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] omap devicetree changes for v4.12, part 2
Date: Wed, 19 Apr 2017 06:48:40 -0700 [thread overview]
Message-ID: <20170419134840.GC29219@localhost> (raw)
In-Reply-To: <58ebe106.066f630a.acb55.1f9aSMTPIN_ADDED_BROKEN@mx.google.com>
On Mon, Apr 10, 2017 at 12:46:06PM -0700, Tony Lindgren wrote:
> The following changes since commit da72e4936445e1081e1223fc58470644da8e8cdb:
>
> Merge branch 'omap-for-v4.12/dt-droid4-v2' into omap-for-v4.12/dt-v2 (2017-03-28 14:00:55 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.12/dt-pt2-signed
>
> for you to fetch changes up to b4e1566e4c5e9fcaf9e17ad741b6094b4f3ddce5:
>
> Merge branch 'omap-for-v4.12/dt-droid4-v2' into omap-for-v4.12/dt-v2 (2017-04-09 16:35:51 -0700)
>
> ----------------------------------------------------------------
> Second set of devicetree changes for omaps for v4.12 merge window
> to configure various devices:
>
> - Enable DCAN on am57xx-idk
>
> - Enable CPSW ethernet0 and 1 on am335x-icev2
>
> - Non-critical fix for droid 4 PMIC interrupt triggering
>
> - Stop disabling SRAM and GPMC on droid 4
>
> - Configure CPCAP PMIC related devices on droid 4 for ADC, charger
> and USB PHY. The charger and USB PHY drivers are still being
> discussed, but the binding for them has been acked by Rob and
> Sebastian so they should be safe to merge together with the ADC
> driver in Linux next that they depend on
Merged, thanks.
-Olof
next parent reply other threads:[~2017-04-19 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58ebe106.066f630a.acb55.1f9aSMTPIN_ADDED_BROKEN@mx.google.com>
2017-04-19 13:48 ` Olof Johansson [this message]
2017-04-10 19:46 [GIT PULL 1/2] omap devicetree changes for v4.12, part 2 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=20170419134840.GC29219@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).