From: Robert Morell <rmorell@nvidia.com>
To: Dilan Lee <dilee@nvidia.com>
Cc: "rpurdie@rpsys.net" <rpurdie@rpsys.net>,
"lethal@linux-sh.org" <lethal@linux-sh.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"arun.murthy@stericsson.com" <arun.murthy@stericsson.com>,
"linus.walleij@stericsson.com" <linus.walleij@stericsson.com>,
Jordan Nien <JNien@nvidia.com>,
Stephen Warren <swarren@nvidia.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] video: Add a callback 'notify_after' for backlight control
Date: Mon, 8 Aug 2011 19:12:58 -0700 [thread overview]
Message-ID: <20110809021258.GM27748@morell.nvidia.com> (raw)
In-Reply-To: <1312855525-21464-1-git-send-email-dilee@nvidia.com>
On Mon, Aug 08, 2011 at 07:05:25PM -0700, Dilan Lee wrote:
[...]
> For example, GPIO backlight_en has to be risen after pwm has been enabled
> to meet panel power on sequence defined in panel specification.
I still think this information is irrelevant/nonsensical here, and
should be omitted entirely..
[...]
> unsigned int lth_brightness;
> int (*notify)(struct device *,
> - int brightness);
> + int brightness);
Please don't change the line above; unlike the one you added after, it
was already lined up properly with its argument list.
Otherwise,
Reviewed-by: Robert Morell <rmorell@nvidia.com>
next prev parent reply other threads:[~2011-08-09 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 2:05 [PATCH] video: Add a callback 'notify_after' for backlight control dilee
2011-08-09 2:12 ` Robert Morell [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-09 2:29 dilee
2011-08-09 2:34 ` Robert Morell
2011-08-09 3:43 ` Arun MURTHY
2011-08-09 8:32 JinGoo Han
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=20110809021258.GM27748@morell.nvidia.com \
--to=rmorell@nvidia.com \
--cc=JNien@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=arun.murthy@stericsson.com \
--cc=dilee@nvidia.com \
--cc=lethal@linux-sh.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=swarren@nvidia.com \
/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