From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/7] ARM: create a cros-ec-keyboard DT fragment
Date: Fri, 18 Jul 2014 16:48:14 +0200 [thread overview]
Message-ID: <20140718144813.GA7149@ulmo> (raw)
In-Reply-To: <1405694740-4090-5-git-send-email-thierry.reding@gmail.com>
On Fri, Jul 18, 2014 at 04:45:38PM +0200, Thierry Reding wrote:
> The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
>
> Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-3.17-dt-cros-ec-kbd
>
> for you to fetch changes up to 1a395e3b4f2e9038964c9eec392ed5300a4b5b83:
>
> ARM: dts: Use the cros-ec-keyboard fragment in exynos5250-snow (2014-06-16 12:11:32 -0600)
>
> ----------------------------------------------------------------
> ARM: create a cros-ec-keyboard DT fragment
>
> This branch contains a series from Doug Anderson that creates a DT
> include file to share some common DT content between Tegra and Exynos
> boards that use cros-ec. I'll be pulling this into Tegra's for-3.17/dt
> branch, and I assume the Samsung maintainers will do something similar.
>
> ----------------------------------------------------------------
> Doug Anderson (3):
> ARM: dts: Create a cros-ec-keyboard fragment
> ARM: tegra: Use the cros-ec-keyboard fragment in venice2
> ARM: dts: Use the cros-ec-keyboard fragment in exynos5250-snow
>
> arch/arm/boot/dts/cros-ec-keyboard.dtsi | 105 ++++++++++++++++++++++++++++++++
> arch/arm/boot/dts/exynos5250-snow.dts | 93 +---------------------------
> arch/arm/boot/dts/tegra124-venice2.dts | 96 +----------------------------
> 3 files changed, 111 insertions(+), 183 deletions(-)
> create mode 100644 arch/arm/boot/dts/cros-ec-keyboard.dtsi
Note that Olof already mentioned that he had pulled this, but he also
said that he hadn't pulled it into anything that feeds into linux-next
so I thought I'd better send it again to make sure it's not forgotten.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140718/6dc736ea/attachment.sig>
next prev parent reply other threads:[~2014-07-18 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 14:45 [GIT PULL 1/7] ARM: tegra: move fuse code out of arch/arm Thierry Reding
2014-07-18 14:45 ` [GIT PULL 2/7] ARM: tegra: core code changes for 3.17 Thierry Reding
2014-07-19 19:31 ` Olof Johansson
2014-07-18 14:45 ` [GIT PULL 3/7] ARM: tegra: rework PCIe regulators Thierry Reding
2014-07-19 19:44 ` Olof Johansson
2014-07-18 14:45 ` [GIT PULL 4/7] ARM: tegra: Add XUSB pad controller support Thierry Reding
2014-07-19 19:50 ` Olof Johansson
2014-07-18 14:45 ` [GIT PULL 5/7] ARM: create a cros-ec-keyboard DT fragment Thierry Reding
2014-07-18 14:48 ` Thierry Reding [this message]
2014-07-18 14:45 ` [GIT PULL 6/7] ARM: tegra: device tree changes for 3.17 Thierry Reding
2014-07-19 19:52 ` Olof Johansson
2014-07-18 14:45 ` [GIT PULL 7/7] ARM: tegra: defconfig updates " Thierry Reding
2014-07-19 19:56 ` Olof Johansson
2014-07-19 19:29 ` [GIT PULL 1/7] ARM: tegra: move fuse code out of arch/arm Olof Johansson
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=20140718144813.GA7149@ulmo \
--to=thierry.reding@gmail.com \
--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).