From: Richard Purdie <rpurdie@rpsys.net>
To: Alberto Panizzo <maramaopercheseimorto@gmail.com>
Cc: linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] backlight: l4f00242t03: Fix regulators handling code in remove function
Date: Sat, 08 May 2010 14:39:55 +0100 [thread overview]
Message-ID: <1273325995.4312.35.camel@rex> (raw)
In-Reply-To: <1272315068.3037.99.camel@realization>
On Mon, 2010-04-26 at 22:51 +0200, Alberto Panizzo wrote:
> Simple swap of regulator free
>
> Signed-off-by: Alberto Panizzo <maramaopercheseimorto@gmail.com>
> ---
> drivers/video/backlight/l4f00242t03.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
Queued in the backlight tree, thanks!
Richard
prev parent reply other threads:[~2010-05-09 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 20:51 [PATCH] backlight: l4f00242t03: Fix regulators handling code in remove function Alberto Panizzo
2010-05-08 13:39 ` Richard Purdie [this message]
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=1273325995.4312.35.camel@rex \
--to=rpurdie@rpsys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maramaopercheseimorto@gmail.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;
as well as URLs for NNTP newsgroup(s).