From: Lee Jones <lee.jones@linaro.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Doug Anderson <dianders@chromium.org>,
swarren@nvidia.com, wsa@the-dreams.de, abrestic@chromium.org,
dgreid@chromium.org, olof@lixom.net, sjg@chromium.org,
linux-samsung-soc@vger.kernel.org, linux-tegra@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, thierry.reding@gmail.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 7/7] ARM: tegra: Add the EC i2c tunnel to tegra124-venice2
Date: Tue, 20 May 2014 09:48:05 +0100 [thread overview]
Message-ID: <20140520084805.GH24991@lee--X1> (raw)
In-Reply-To: <53629B29.3050702@wwwdotorg.org>
> > This adds the EC i2c tunnel (and devices under it) to the
> > tegra124-venice2 device tree.
>
> I'll happily take this into the Tegra tree once the patch containing the
> binding it uses is applied.
All other patches applied. Take this when ready.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-05-20 8:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 17:44 [PATCH v3 0/7] Add cros_ec changes for newer boards Doug Anderson
2014-04-30 17:44 ` [PATCH v3 1/7] mfd: cros_ec: spi: calculate delay between transfers correctly Doug Anderson
2014-05-20 8:43 ` Lee Jones
2014-04-30 17:44 ` [PATCH v3 2/7] mfd: cros_ec: spi: Add mutex to cros_ec_spi Doug Anderson
2014-05-20 8:44 ` Lee Jones
2014-04-30 17:44 ` [PATCH v3 3/7] mfd: cros_ec: spi: Make the cros_ec_spi timeout more reliable Doug Anderson
2014-05-20 8:45 ` Lee Jones
2014-04-30 17:44 ` [PATCH v3 4/7] mfd: cros_ec: spi: Increase cros_ec_spi deadline from 5ms to 100ms Doug Anderson
2014-05-20 8:45 ` Lee Jones
2014-04-30 17:44 ` [PATCH v3 5/7] mfd: cros_ec: Sync to the latest cros_ec_commands.h from EC sources Doug Anderson
2014-05-20 8:46 ` Lee Jones
2014-06-11 10:37 ` Paul Bolle
2014-06-11 15:11 ` Doug Anderson
2014-06-13 8:08 ` Paul Bolle
2014-06-13 15:22 ` Doug Anderson
2014-06-17 8:53 ` Paul Bolle
2014-06-17 16:20 ` Stephen Warren
2014-06-17 16:43 ` Paul Bolle
2014-04-30 17:44 ` [PATCH v3 6/7] i2c: ChromeOS EC tunnel driver Doug Anderson
2014-05-01 19:05 ` Stephen Warren
2014-05-19 10:50 ` Wolfram Sang
2014-05-19 17:22 ` Lee Jones
2014-05-19 22:19 ` Wolfram Sang
2014-05-20 8:43 ` Lee Jones
2014-05-20 8:47 ` Lee Jones
2014-05-20 17:35 ` Stephen Warren
2014-04-30 17:44 ` [PATCH v3 7/7] ARM: tegra: Add the EC i2c tunnel to tegra124-venice2 Doug Anderson
2014-05-01 19:06 ` Stephen Warren
2014-05-20 8:48 ` Lee Jones [this message]
2014-06-16 19:01 ` Stephen Warren
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=20140520084805.GH24991@lee--X1 \
--to=lee.jones@linaro.org \
--cc=abrestic@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dgreid@chromium.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-tegra@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=sjg@chromium.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=wsa@the-dreams.de \
/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