From: Dmitry Osipenko <digetx@gmail.com>
To: Peter Geis <pgwipeout@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Matt Merhar <mattmerhar@protonmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Bob Ham <rah@settrans.net>, Leonardo Bras <leobras.c@gmail.com>,
Michael Brougham <jusplainmike@gmail.com>
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] ARM: tegra: Add device-tree for Ouya
Date: Mon, 5 Oct 2020 17:29:53 +0300 [thread overview]
Message-ID: <e7662043-7f8c-4df1-df5c-bef34983c0d9@gmail.com> (raw)
In-Reply-To: <20201004133114.845230-2-pgwipeout@gmail.com>
04.10.2020 16:31, Peter Geis пишет:
> The Ouya was the sole device produced by Ouya Inc in 2013.
> It was a game console originally running Android 5 on top of Linux 3.1.10.
>
> This patch adds the device tree supporting the Ouya.
> It has been tested on the original variant with Samsung ram.
>
> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> ---
Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
next prev parent reply other threads:[~2020-10-05 14:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 13:31 [PATCH v3 0/3] Support NVIDIA Tegra-based Ouya game console Peter Geis
2020-10-04 13:31 ` [PATCH v3 1/3] ARM: tegra: Add device-tree for Ouya Peter Geis
2020-10-05 14:02 ` Dmitry Osipenko
2020-10-05 14:22 ` Peter Geis
2020-10-05 14:29 ` Dmitry Osipenko
2020-10-05 14:29 ` Dmitry Osipenko [this message]
2020-10-04 13:31 ` [PATCH v3 2/3] dt-bindings: Add vendor prefix for Ouya Inc Peter Geis
2020-10-05 14:32 ` Dmitry Osipenko
2020-10-04 13:31 ` [PATCH v3 3/3] dt-bindings: ARM: tegra: Add Ouya game console Peter Geis
2020-10-05 14:32 ` Dmitry Osipenko
2020-10-05 15:47 ` [PATCH v3 0/3] Support NVIDIA Tegra-based " Thierry Reding
2020-10-07 7:22 ` Stefan Agner
2020-10-07 13:36 ` Bob Ham
2020-10-07 13:53 ` Dmitry Osipenko
2020-10-07 14:01 ` Dmitry Osipenko
2020-10-07 16:08 ` Stephen Warren
2020-10-07 17:18 ` Peter Geis
2020-10-08 5:05 ` Dmitry Osipenko
2020-11-10 17:42 ` Thierry Reding
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=e7662043-7f8c-4df1-df5c-bef34983c0d9@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=jusplainmike@gmail.com \
--cc=leobras.c@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=pgwipeout@gmail.com \
--cc=rah@settrans.net \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).