From: Daniel Thompson <daniel.thompson@linaro.org>
To: Felix Brack <fb@ltec.ch>
Cc: linux-fbdev@vger.kernel.org, lee.jones@linaro.org,
jingoohan1@gmail.com, b.zolnierkie@samsung.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add support for ORISE OTM3225A LCD SoC
Date: Wed, 20 Dec 2017 16:57:36 +0000 [thread overview]
Message-ID: <20171220165736.e247aggbkl4qir23@oak.lan> (raw)
In-Reply-To: <cde8376c-8217-6cfd-0a0a-b90b75892bea@ltec.ch>
On Wed, Dec 20, 2017 at 05:35:24PM +0100, Felix Brack wrote:
> Just a gentle echo request ;-)
> Is there something completely wrong with this patch or am I just too
> impatient?
>
> regards Felix
>
> On 03.11.2017 14:09, Felix Brack wrote:
> > This patch adds a LCD driver supporting the OTM3225A LCD SoC
> > from ORISE Technology. This device can drive TFT LC panels having a
> > resolution of 240x320 pixels. After initializing the OTM3225A using
> > it's SPI interface it switches to use 16-bib RGB as external
> > display interface.
Was this a backlight driver? I've just noticed all the backlight
maintainers on Cc: but the subject doesn't make this obvious and even
with you quoting the patch header I still can't be entirely sure!
As a result I think its very likely the patch simply got overlooked
because it didn't look much like a backlight driver when filtering
e-mail. Patches that can't be easily categorized from the subject
line will often get overlooked.
So, asssuming this was a backlight driver, could you resend the patch
with an updated description and a subject line commenting:
[PATCH] backlight: otm3225a:
Daniel.
next prev parent reply other threads:[~2017-12-20 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 13:09 [PATCH] Add support for ORISE OTM3225A LCD SoC Felix Brack
2017-12-20 16:35 ` Felix Brack
2017-12-20 16:57 ` Daniel Thompson [this message]
2017-12-20 17:08 ` Felix Brack
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=20171220165736.e247aggbkl4qir23@oak.lan \
--to=daniel.thompson@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=fb@ltec.ch \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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