From: Stephen Warren <swarren@wwwdotorg.org>
To: Doug Anderson <dianders@chromium.org>,
Stephen Warren <swarren@nvidia.com>,
Thierry Reding <treding@nvidia.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
olof@lixom.net
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux@arm.linux.org.uk, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, galak@codeaurora.org,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: dts: Create a cros-ec-keyboard fragment
Date: Mon, 16 Jun 2014 12:14:22 -0600 [thread overview]
Message-ID: <539F33FE.8040501@wwwdotorg.org> (raw)
In-Reply-To: <1401920421-25729-1-git-send-email-dianders@chromium.org>
On 06/04/2014 04:20 PM, Doug Anderson wrote:
> All ChromeOS ARM devices that have the standard "CrOS EC" have the
> same keyboard mapping. It's silly to include this same definition
> everywhere. Let's create a "dtsi" fragment that we can include from
> many different boards.
>
> This fragment is based on what's currently in tegra124-venice2.dts
I've applied this series to Tegra's for-3.17/dt-cros-ec-kbd branch. I'll
send a pull request to arm-soc shortly.
next prev parent reply other threads:[~2014-06-16 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 22:20 [PATCH 1/3] ARM: dts: Create a cros-ec-keyboard fragment Doug Anderson
2014-06-04 22:20 ` [PATCH 2/3] ARM: tegra: Use the cros-ec-keyboard fragment in venice2 Doug Anderson
2014-06-04 22:20 ` [PATCH 3/3] ARM: dts: Use the cros-ec-keyboard fragment in exynos5250-snow Doug Anderson
2014-06-05 15:51 ` [PATCH 1/3] ARM: dts: Create a cros-ec-keyboard fragment Stephen Warren
2014-06-05 16:12 ` Olof Johansson
2014-06-16 18:14 ` Stephen Warren [this message]
2014-06-16 18:30 ` Doug Anderson
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=539F33FE.8040501@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=javier.martinez@collabora.co.uk \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@nvidia.com \
--cc=tomasz.figa@gmail.com \
--cc=treding@nvidia.com \
/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