From: Stefan Agner <stefan-XLVq0VzYD2Y@public.gmane.org>
To: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
marcel-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH v2 2/3] drm/panel: add support for EDT panels
Date: Thu, 15 May 2014 11:39:41 +0200 [thread overview]
Message-ID: <cc51075ad7c00d6b08d28834d651b198@agner.ch> (raw)
In-Reply-To: <1400146519.4102.30.camel-+qGW7pzALmz7o/J7KWpOmN53zsg1cpMQ@public.gmane.org>
Am 2014-05-15 11:35, schrieb Philipp Zabel:
> Am Donnerstag, den 15.05.2014, 11:12 +0200 schrieb Thierry Reding:
<snip>
>> I also noticed that Philipp's patch doesn't actually introduce the
>> device tree bindings, so that will have to be added as well.
>
> Hmm, yes. Should I take over the edt,et070080dh6.txt from Stefan's
> series and repost all, or can I just hand in the missing
> edt,etm0700g0dh6.txt separately?
Just sent a revision of my patch which doesn't contain that text file
anymore, hence for me it would be preferable if you can add both
files...
--
Stefan
next prev parent reply other threads:[~2014-05-15 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 21:45 [PATCH v2 0/4] ARM: tegra: initial support for Colibri T30 stefan
[not found] ` <cover.1400103181.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-05-14 21:45 ` [PATCH v2 1/3] ARM: tegra: enable MCP251x CAN controller and DS1307 RTC stefan-XLVq0VzYD2Y
[not found] ` <4cc13e0aba03a5b2d3e5f4049d252956342b1dad.1400103181.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-05-15 18:15 ` Stephen Warren
2014-05-14 21:45 ` [PATCH v2 3/3] ARM: tegra: initial add of Colibri T30 stefan-XLVq0VzYD2Y
[not found] ` <a8f01e573dcb7d563833ddcda30567e8ac7626ed.1400103181.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-05-15 18:37 ` Stephen Warren
2014-05-14 21:45 ` [PATCH v2 2/3] drm/panel: add support for EDT panels stefan
[not found] ` <35c081171a3d9a9401767601c02a12e266b37dd0.1400103181.git.stefan-XLVq0VzYD2Y@public.gmane.org>
2014-05-15 7:51 ` Thierry Reding
2014-05-15 8:24 ` Stefan Agner
2014-05-15 9:12 ` Thierry Reding
2014-05-15 9:35 ` Philipp Zabel
[not found] ` <1400146519.4102.30.camel-+qGW7pzALmz7o/J7KWpOmN53zsg1cpMQ@public.gmane.org>
2014-05-15 9:39 ` Stefan Agner [this message]
2014-05-15 8:27 ` Philipp Zabel
[not found] ` <1400142449.4102.16.camel-+qGW7pzALmz7o/J7KWpOmN53zsg1cpMQ@public.gmane.org>
2014-05-15 9:08 ` Thierry Reding
2014-05-15 9:30 ` Philipp Zabel
2014-05-15 9:36 ` Stefan Agner
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=cc51075ad7c00d6b08d28834d651b198@agner.ch \
--to=stefan-xlvq0vzyd2y@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marcel-mitwqZ+T+m9Wk0Htik3J/w@public.gmane.org \
--cc=p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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 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).