From: Ryan Mallon <rmallon@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
devicetree-discuss@lists.ozlabs.org,
Samuel Ortiz <sameo@linux.intel.com>,
Richard Purdie <rpurdie@rpsys.net>,
linux-fbdev@vger.kernel.org,
Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
Subject: Re: [PATCH v3 3/3] backlight: as3711: add OF support
Date: Tue, 26 Mar 2013 10:09:30 +1100 [thread overview]
Message-ID: <5150D92A.4000206@gmail.com> (raw)
In-Reply-To: <20130325154046.82d9337f25cec12b9fa03625@linux-foundation.org>
On 26/03/13 09:40, Andrew Morton wrote:
> On Fri, 22 Mar 2013 17:15:49 +0100 Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
>
>> Add support for configuring AS3711 backlight driver from DT.
>>
>> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
>> Reviwed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>> ---
>> drivers/video/backlight/as3711_bl.c | 118 ++++++++++++++++++++++++++++++++++-
>> 1 files changed, 117 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/video/backlight/as3711_bl.c b/drivers/video/backlight/as3711_bl.c
>> index 41d52fe..123887c 100644
>> --- a/drivers/video/backlight/as3711_bl.c
>> +++ b/drivers/video/backlight/as3711_bl.c
>> @@ -258,6 +258,109 @@ static int as3711_bl_register(struct platform_device *pdev,
>> return 0;
>> }
>>
>> +static int as3711_backlight_parse_dt(struct device *dev)
>> +{
>> + struct as3711_bl_pdata *pdata = dev_get_platdata(dev);
>> + struct device_node *bl =
>> + of_find_node_by_name(dev->parent->of_node, "backlight"), *fb;
>> + int ret;
>
> It's tidier to do
>
> struct device_node *bl;
>
> bl = of_find_node_by_name(dev->parent->of_node, "backlight"), *fb;
>
> and avoid the 80-col trickery.
The other reason being that it now becomes much more apparent that *fb
is not an argument to of_find_node_by_name(), but a second variable of
type struct device_node :-).
~Ryan
prev parent reply other threads:[~2013-03-25 23:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 16:15 [PATCH v3 0/3] DT support for AS3711 MFD, regulator and backlight drivers Guennadi Liakhovetski
2013-03-22 16:15 ` [PATCH v3 1/3] mfd: as3711: add OF support Guennadi Liakhovetski
2013-03-22 16:34 ` Samuel Ortiz
2013-03-22 16:15 ` [PATCH v3 2/3] regulator: " Guennadi Liakhovetski
2013-03-22 18:53 ` Mark Brown
[not found] ` <20130322185333.GN22890-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2013-03-22 22:27 ` Guennadi Liakhovetski
2013-03-25 1:08 ` Mark Brown
2013-03-22 16:15 ` [PATCH v3 3/3] backlight: " Guennadi Liakhovetski
2013-03-25 5:12 ` Jingoo Han
[not found] ` <00da01ce2917$54856ce0$fd9046a0$%han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-03-25 10:14 ` Mark Brown
2013-03-25 10:52 ` Guennadi Liakhovetski
2013-03-25 23:39 ` Jingoo Han
2013-03-25 22:40 ` Andrew Morton
2013-03-25 23:09 ` Ryan Mallon [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=5150D92A.4000206@gmail.com \
--to=rmallon@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=g.liakhovetski+renesas@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rpurdie@rpsys.net \
--cc=sameo@linux.intel.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).