From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: use correct audio CODEC on Jetson TK1
Date: Sat, 26 Apr 2014 00:11:15 +0200 [thread overview]
Message-ID: <20140425221114.GA1352@ulmo> (raw)
In-Reply-To: <1398443012-17212-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On Fri, Apr 25, 2014 at 10:23:32AM -0600, Stephen Warren wrote:
> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> Jetson TK1 contains an RT5639 not an RT5640. While the two are extremely
> similar and mostly compatible, we should still use the correct device
> name in the device tree. I had meant to fix this before applying the
> initial DT, but this issue slipped my mind.
>
> Signed-off-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> ---
> arch/arm/boot/dts/tegra124-jetson-tk1.dts | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: use correct audio CODEC on Jetson TK1
Date: Sat, 26 Apr 2014 00:11:15 +0200 [thread overview]
Message-ID: <20140425221114.GA1352@ulmo> (raw)
In-Reply-To: <1398443012-17212-1-git-send-email-swarren@wwwdotorg.org>
On Fri, Apr 25, 2014 at 10:23:32AM -0600, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Jetson TK1 contains an RT5639 not an RT5640. While the two are extremely
> similar and mostly compatible, we should still use the correct device
> name in the device tree. I had meant to fix this before applying the
> initial DT, but this issue slipped my mind.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> arch/arm/boot/dts/tegra124-jetson-tk1.dts | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Thierry Reding <treding@nvidia.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140426/d8cb5e3b/attachment.sig>
next prev parent reply other threads:[~2014-04-25 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 16:23 [PATCH] ARM: tegra: use correct audio CODEC on Jetson TK1 Stephen Warren
2014-04-25 16:23 ` Stephen Warren
[not found] ` <1398443012-17212-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-04-25 22:11 ` Thierry Reding [this message]
2014-04-25 22:11 ` Thierry Reding
2014-04-28 16:05 ` Stephen Warren
2014-04-28 16:05 ` 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=20140425221114.GA1352@ulmo \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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.