From: holgerschurig@gmail.com (Holger Schurig)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] drm/panel: simple: Add support for Innolux AT070TN92
Date: Thu, 21 Apr 2016 14:11:19 +0200 [thread overview]
Message-ID: <877ffrp3fc.fsf@gmail.com> (raw)
In-Reply-To: <20160420134036.GA7470@ulmo.ba.sec> (Thierry Reding's message of "Wed, 20 Apr 2016 15:40:36 +0200")
Thierry Reding <thierry.reding@gmail.com> writes:
> Applied, thanks.
I once read that this is the recommended way to go, instead of
specifying the timings in the device tree. Why is this so? Any new
display just increases the .text size of the kernel unnessary.
Did this idea stem from the era where bootloaders like Barebox couldn't
modify the DT ad-hoc before handing it over to the kernel?
next prev parent reply other threads:[~2016-04-21 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 13:37 [PATCH v2] drm/panel: simple: Add support for Innolux AT070TN92 Boris Brezillon
2016-04-20 13:40 ` Thierry Reding
2016-04-21 12:11 ` Holger Schurig [this message]
2016-04-22 22:30 ` 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=877ffrp3fc.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).