From: Alex Courbot <acourbot@nvidia.com>
To: Mark Zhang <nvmarkzhang@gmail.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"David Lanzendörfer" <david.lanzendoerfer@o2s.ch>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Stephen Warren" <swarren@wwwdotorg.org>
Subject: Re: Naming convention DSI + device tree
Date: Thu, 23 May 2013 18:55:21 +0900 [thread overview]
Message-ID: <519DE789.5020308@nvidia.com> (raw)
In-Reply-To: <519C64AB.2090708@gmail.com>
On 05/22/2013 03:24 PM, Mark Zhang wrote:
> Cool. Alex, do you know any updates on DSI part of CDF? I recall few
> months ago, Laurent wrote mail to share some infos about the CDF
> discussions, and it mentioned that the DSI will be considered in next
> version of CDF... you know, for t114, the DSI support is a must.
I will make sure to discuss this detail with Laurent as he comes for
LinuxCon next week. ;)
Alex.
WARNING: multiple messages have this Message-ID (diff)
From: acourbot@nvidia.com (Alex Courbot)
To: linux-arm-kernel@lists.infradead.org
Subject: Naming convention DSI + device tree
Date: Thu, 23 May 2013 18:55:21 +0900 [thread overview]
Message-ID: <519DE789.5020308@nvidia.com> (raw)
In-Reply-To: <519C64AB.2090708@gmail.com>
On 05/22/2013 03:24 PM, Mark Zhang wrote:
> Cool. Alex, do you know any updates on DSI part of CDF? I recall few
> months ago, Laurent wrote mail to share some infos about the CDF
> discussions, and it mentioned that the DSI will be considered in next
> version of CDF... you know, for t114, the DSI support is a must.
I will make sure to discuss this detail with Laurent as he comes for
LinuxCon next week. ;)
Alex.
next prev parent reply other threads:[~2013-05-23 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 18:17 Naming convention DSI + device tree David Lanzendörfer
2013-05-15 22:28 ` Stephen Warren
2013-05-16 7:15 ` David Lanzendörfer
[not found] ` <20130516071537.GA13573-cEukqlNQfh4fv37vnLkPlQ@public.gmane.org>
2013-05-16 18:17 ` Stephen Warren
2013-05-16 18:17 ` Stephen Warren
2013-05-16 19:50 ` David Lanzendörfer
2013-05-16 19:50 ` David Lanzendörfer
[not found] ` <519522C1.5010107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-17 5:36 ` Alex Courbot
2013-05-17 5:36 ` Alex Courbot
[not found] ` <5195C1E2.4020009-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-05-17 19:39 ` Stephen Warren
2013-05-17 19:39 ` Stephen Warren
2013-05-22 6:24 ` Mark Zhang
2013-05-22 6:24 ` Mark Zhang
2013-05-23 9:55 ` Alex Courbot [this message]
2013-05-23 9:55 ` Alex Courbot
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=519DE789.5020308@nvidia.com \
--to=acourbot@nvidia.com \
--cc=david.lanzendoerfer@o2s.ch \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nvmarkzhang@gmail.com \
--cc=swarren@wwwdotorg.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.