From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: dts: Create a cros-ec-keyboard fragment
Date: Thu, 05 Jun 2014 09:51:53 -0600 [thread overview]
Message-ID: <53909219.6090200@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
This series looks fine to me. Given it touches both Tegra and Exynos,
should it be merged into a topic branch in arm-soc, so that it can be
pulled into both Tegra/Exynos trees to resolve any conflicts. So,
Acked-by: Stephen Warren <swarren@nvidia.com>
If you want, I'm happy to apply this to a topic branch and send a pull
request to arm-soc.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Doug Anderson <dianders@chromium.org>,
olof@lixom.net, "arm@kernel.org" <arm@kernel.org>
Cc: Stephen Warren <swarren@nvidia.com>,
Thierry Reding <treding@nvidia.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
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: Thu, 05 Jun 2014 09:51:53 -0600 [thread overview]
Message-ID: <53909219.6090200@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
This series looks fine to me. Given it touches both Tegra and Exynos,
should it be merged into a topic branch in arm-soc, so that it can be
pulled into both Tegra/Exynos trees to resolve any conflicts. So,
Acked-by: Stephen Warren <swarren@nvidia.com>
If you want, I'm happy to apply this to a topic branch and send a pull
request to arm-soc.
next prev parent reply other threads:[~2014-06-05 15:51 UTC|newest]
Thread overview: 18+ 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 ` Doug Anderson
2014-06-04 22:20 ` 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 ` Doug Anderson
[not found] ` <1401920421-25729-1-git-send-email-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-06-04 22:20 ` [PATCH 3/3] ARM: dts: Use the cros-ec-keyboard fragment in exynos5250-snow Doug Anderson
2014-06-04 22:20 ` Doug Anderson
2014-06-04 22:20 ` Doug Anderson
2014-06-05 15:51 ` Stephen Warren [this message]
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-05 16:12 ` Olof Johansson
2014-06-16 18:14 ` Stephen Warren
2014-06-16 18:14 ` Stephen Warren
2014-06-16 18:14 ` Stephen Warren
2014-06-16 18:30 ` Doug Anderson
2014-06-16 18:30 ` Doug Anderson
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=53909219.6090200@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.