From: Benoit Cousson <b-cousson@ti.com>
To: florian.vaussard@epfl.ch
Cc: Linus Walleij <linus.walleij@linaro.org>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
Grant Likely <grant.likely@secretlab.ca>,
Vaibhav Hiremath <hvaibhav@ti.com>,
Rob Herring <rob.herring@calxeda.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] gpio/twl4030: get platform data from device tree
Date: Mon, 10 Sep 2012 10:29:55 +0200 [thread overview]
Message-ID: <504DA503.5050901@ti.com> (raw)
In-Reply-To: <504DA20D.7020903@epfl.ch>
Hi Florian,
On 09/10/2012 10:17 AM, Florian Vaussard wrote:
> Hello Benoit,
>
> Le 07/09/2012 19:33, Benoit Cousson a écrit :
>> Hi Florian,
>>
>> I've just noticed that this patch is reporting some CHECK issues.
>>
>> d1f5052 - gpio/twl4030: get platform data from device tree
>> CHECK: Alignment should match open parenthesis
>> #66: FILE: drivers/gpio/gpio-twl4030.c:412:
>> + of_property_read_u32(dev->of_node, "ti,debounce",
>> + &omap_twl_info->debounce);
>>
>> CHECK: Alignment should match open parenthesis
>> #68: FILE: drivers/gpio/gpio-twl4030.c:414:
>> + of_property_read_u32(dev->of_node, "ti,mmc-cd",
>> + (u32 *)&omap_twl_info->mmc_cd);
>>
>> CHECK: Alignment should match open parenthesis
>> #70: FILE: drivers/gpio/gpio-twl4030.c:416:
>> + of_property_read_u32(dev->of_node, "ti,pullups",
>> + &omap_twl_info->pullups);
>>
>> CHECK: Alignment should match open parenthesis
>> #72: FILE: drivers/gpio/gpio-twl4030.c:418:
>> + of_property_read_u32(dev->of_node, "ti,pulldowns",
>> + &omap_twl_info->pulldowns);
>>
>> CHECK: Alignment should match open parenthesis
>> + pdata->pullups, pdata->pulldowns,
>>
>> CHECK: Alignment should match open parenthesis
>> #139: FILE: drivers/gpio/gpio-twl4030.c:479:
>> + dev_dbg(&pdev->dev, "debounce %.03x %.01x --> %d\n",
>> + pdata->debounce, pdata->mmc_cd,
>>
>> total: 0 errors, 0 warnings, 6 checks, 118 lines checked
>>
>>
>> I fixed them since it was trivial, but next time you should ensure
>> that the patch pass checkpatch before posting.
>
> Sorry for these errors. I however checked my patches before submitting,
> and had no such warnings. I redone, and remarked that these warnings
> appear only with the "--strict" option, which is not enabled by default.
> Is this the recommended guideline? Thus why not enabling it by default?
That's a pretty good question :-)
Maybe the --strict is more a nice to have than a strong requirement?
Anyway, we'd better run checkpatch with --strict and thus fix any
cosmetic details that might be in the patch.
>> Just let me know if you have any issue with the following update.
>
> I will test, but should not have any issue with your fix.
>
> Thank you very much for fixing my patch, I send you a virtual chocolate
> from Switzerland!
Cool, I love chocolate. That being said, I'm not sure how tasteful will
be the *virtual* chocolate.
Regards,
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] gpio/twl4030: get platform data from device tree
Date: Mon, 10 Sep 2012 10:29:55 +0200 [thread overview]
Message-ID: <504DA503.5050901@ti.com> (raw)
In-Reply-To: <504DA20D.7020903@epfl.ch>
Hi Florian,
On 09/10/2012 10:17 AM, Florian Vaussard wrote:
> Hello Benoit,
>
> Le 07/09/2012 19:33, Benoit Cousson a ?crit :
>> Hi Florian,
>>
>> I've just noticed that this patch is reporting some CHECK issues.
>>
>> d1f5052 - gpio/twl4030: get platform data from device tree
>> CHECK: Alignment should match open parenthesis
>> #66: FILE: drivers/gpio/gpio-twl4030.c:412:
>> + of_property_read_u32(dev->of_node, "ti,debounce",
>> + &omap_twl_info->debounce);
>>
>> CHECK: Alignment should match open parenthesis
>> #68: FILE: drivers/gpio/gpio-twl4030.c:414:
>> + of_property_read_u32(dev->of_node, "ti,mmc-cd",
>> + (u32 *)&omap_twl_info->mmc_cd);
>>
>> CHECK: Alignment should match open parenthesis
>> #70: FILE: drivers/gpio/gpio-twl4030.c:416:
>> + of_property_read_u32(dev->of_node, "ti,pullups",
>> + &omap_twl_info->pullups);
>>
>> CHECK: Alignment should match open parenthesis
>> #72: FILE: drivers/gpio/gpio-twl4030.c:418:
>> + of_property_read_u32(dev->of_node, "ti,pulldowns",
>> + &omap_twl_info->pulldowns);
>>
>> CHECK: Alignment should match open parenthesis
>> + pdata->pullups, pdata->pulldowns,
>>
>> CHECK: Alignment should match open parenthesis
>> #139: FILE: drivers/gpio/gpio-twl4030.c:479:
>> + dev_dbg(&pdev->dev, "debounce %.03x %.01x --> %d\n",
>> + pdata->debounce, pdata->mmc_cd,
>>
>> total: 0 errors, 0 warnings, 6 checks, 118 lines checked
>>
>>
>> I fixed them since it was trivial, but next time you should ensure
>> that the patch pass checkpatch before posting.
>
> Sorry for these errors. I however checked my patches before submitting,
> and had no such warnings. I redone, and remarked that these warnings
> appear only with the "--strict" option, which is not enabled by default.
> Is this the recommended guideline? Thus why not enabling it by default?
That's a pretty good question :-)
Maybe the --strict is more a nice to have than a strong requirement?
Anyway, we'd better run checkpatch with --strict and thus fix any
cosmetic details that might be in the patch.
>> Just let me know if you have any issue with the following update.
>
> I will test, but should not have any issue with your fix.
>
> Thank you very much for fixing my patch, I send you a virtual chocolate
> from Switzerland!
Cool, I love chocolate. That being said, I'm not sure how tasteful will
be the *virtual* chocolate.
Regards,
Benoit
next prev parent reply other threads:[~2012-09-10 8:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 7:46 [PATCH v2 0/2] gpio-twl4030: add new device tree properties Florian Vaussard
2012-09-05 7:46 ` Florian Vaussard
2012-09-05 7:46 ` [PATCH 1/2] gpio/twl4030: get platform data from device tree Florian Vaussard
2012-09-05 7:46 ` Florian Vaussard
[not found] ` <1346831186-29947-2-git-send-email-florian.vaussard-p8DiymsW2f8@public.gmane.org>
2012-09-07 17:33 ` Benoit Cousson
2012-09-07 17:33 ` Benoit Cousson
2012-09-10 8:17 ` Florian Vaussard
2012-09-10 8:17 ` Florian Vaussard
2012-09-10 8:29 ` Benoit Cousson [this message]
2012-09-10 8:29 ` Benoit Cousson
[not found] ` <504DA503.5050901-l0cyMroinI0@public.gmane.org>
2012-09-10 8:40 ` Florian Vaussard
2012-09-10 8:40 ` Florian Vaussard
2012-09-05 7:46 ` [PATCH 2/2] ARM: dts: omap3: Add gpio-twl4030 properties for BeagleBoard and omap3-EVM Florian Vaussard
2012-09-05 7:46 ` Florian Vaussard
2012-09-05 14:41 ` [PATCH v2 0/2] gpio-twl4030: add new device tree properties Benoit Cousson
2012-09-05 14:41 ` Benoit Cousson
2012-09-06 20:51 ` Tony Lindgren
2012-09-06 20:51 ` Tony Lindgren
2012-09-07 8:55 ` Benoit Cousson
2012-09-07 8:55 ` Benoit Cousson
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=504DA503.5050901@ti.com \
--to=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=florian.vaussard@epfl.ch \
--cc=grant.likely@secretlab.ca \
--cc=hvaibhav@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=tony@atomide.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 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.