From: Andrew Morton <akpm@linux-foundation.org>
To: "Kim, Milo" <Milo.Kim@ti.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Richard Purdie" <rpurdie@rpsys.net>
Subject: Re: [PATCH v2] backlight: new backlight driver for LP855x devices
Date: Thu, 26 Jan 2012 15:46:51 -0800 [thread overview]
Message-ID: <20120126154651.767c4e55.akpm@linux-foundation.org> (raw)
In-Reply-To: <B567DBAB974C0544994013492B949F8E3812CD3EE5@EXMAIL03.scwf.nsc.com>
On Tue, 24 Jan 2012 22:24:02 -0800
"Kim, Milo" <Milo.Kim@ti.com> wrote:
> This patch supports TI LP8550/LP8551/LP8852/LP8553/LP8556 backlight driver.
>
> The brightness can be controlled by the I2C or PWM input.
> The lp855x driver provides both modes.
> For the PWM control, pwm-specific functions can be defined in the platform data.
> And some information can be read via the sysfs(lp855x device attributes).
>
> For the details, please refer to 'Documentation/backlight/lp855x-driver.txt'.
>
I had a few little problems here.
- For some reason my email client doesn't like MIME quoted-printable
and cannot correctly extract the plain text. It appears that
globally deleting =\n and globally replacing =3D with = fixes things.
Ho hum. I really should go see if this has been fixed, or hassle
the sylpheed developer(s).
- The driver generates a great storm of scripts/checkpatch.pl
whitespace warnings. Things like using eight spaces instead of a
tab. These really should be fixed, so please take a look at the
checkpatch output then resend?
next prev parent reply other threads:[~2012-01-26 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 6:24 [PATCH v2] backlight: new backlight driver for LP855x devices Kim, Milo
2012-01-26 23:46 ` Andrew Morton [this message]
2012-01-27 2:06 ` Kim, Milo
2012-01-27 2:08 ` Kim, Milo
2012-01-27 9:12 ` Kim, Milo
-- strict thread matches above, loose matches on Subject: below --
2012-01-25 6:25 Kim, Milo
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=20120126154651.767c4e55.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Milo.Kim@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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.