From: Stephen Warren <swarren@wwwdotorg.org>
To: arm@kernel.org, Mike Turquette <mturquette@linaro.org>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/3] ARM: tegra: remove UART5/UARTE from tegra124.dtsi
Date: Mon, 14 Apr 2014 14:53:00 -0600 [thread overview]
Message-ID: <534C4AAC.2020207@wwwdotorg.org> (raw)
In-Reply-To: <1396383197-5979-1-git-send-email-swarren@wwwdotorg.org>
On 04/01/2014 02:13 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Tegra124 only has 4 UARTs. Parts of the documentation hint at a fifth
> UART, but this appears to be left-over from earlier SoC documentation.
> Remove the non-existent DT node for UART5.
arm-soc maintainers, I'm hoping this will be applied as a fix for v3.15
through the arm-soc tree. Do you want me to send a pull request with the
series? Patch 2/3 does touch files in drivers/clk; are you waiting for
Mike's ack on it? It already has Peter's ack as Tegra clock driver
maintainer.
Thanks.
prev parent reply other threads:[~2014-04-14 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 20:13 [PATCH 1/3] ARM: tegra: remove UART5/UARTE from tegra124.dtsi Stephen Warren
[not found] ` <1396383197-5979-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-04-01 20:13 ` [PATCH 2/3] clk: tegra: remove non-existent clocks Stephen Warren
2014-04-02 8:10 ` Peter De Schrijver
[not found] ` <1396383197-5979-2-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-04-23 16:24 ` Stephen Warren
2014-04-01 20:13 ` [PATCH 3/3] dt: tegra: remove non-existent clock IDs Stephen Warren
2014-04-14 20:53 ` Stephen Warren [this message]
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=534C4AAC.2020207@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arm@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pdeschrijver@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=swarren@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