From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] bcm2835-dt-next-2017-01-17
Date: Tue, 17 Jan 2017 21:10:43 +1100 [thread overview]
Message-ID: <20170117101043.28802-1-eric@anholt.net> (raw)
Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
are available in the git repository at:
https://github.com/anholt/linux tags/bcm2835-dt-next-2017-01-17
for you to fetch changes up to 38742ca2b8b21bfc2a2cc24278b58485ff781644:
ARM: bcm/dt: Enable the VEC IP on all RaspberryPi boards (2017-01-16 21:50:26 +1100)
----------------------------------------------------------------
This pull request brings in the DT changes for VEC (TV-out) on
Raspberry Pi.
----------------------------------------------------------------
Boris Brezillon (2):
ARM: bcm/dt: Add VEC node in bcm283x.dtsi
ARM: bcm/dt: Enable the VEC IP on all RaspberryPi boards
arch/arm/boot/dts/bcm2835-rpi.dtsi | 5 +++++
arch/arm/boot/dts/bcm283x.dtsi | 8 ++++++++
2 files changed, 13 insertions(+)
next reply other threads:[~2017-01-17 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 10:10 Eric Anholt [this message]
2017-01-18 1:11 ` [GIT PULL] bcm2835-dt-next-2017-01-17 Florian Fainelli
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=20170117101043.28802-1-eric@anholt.net \
--to=eric@anholt.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).