From: Nishanth Menon <nm@ti.com>
To: Jingoo Han <jg1.han@samsung.com>, "'Mark Brown'" <broonie@linaro.org>
Cc: "'Liam Girdwood'" <lgirdwood@gmail.com>,
<linux-kernel@vger.kernel.org>, "'Balaji T K'" <balajitk@ti.com>
Subject: Re: [PATCH 11/11] regulator: twl: Fix checkpatch issue
Date: Mon, 14 Oct 2013 13:32:11 -0500 [thread overview]
Message-ID: <525C38AB.3060002@ti.com> (raw)
In-Reply-To: <000a01cec8bb$13bf5970$3b3e0c50$%han@samsung.com>
On 10/14/2013 03:55 AM, Jingoo Han wrote:
> Fix the following checkpatch warnings.
>
> WARNING: please, no space before tabs
> WARNING: space prohibited between function name and open parenthesis '('
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
> drivers/regulator/twl-regulator.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/regulator/twl-regulator.c b/drivers/regulator/twl-regulator.c
> index 8ebd785..fed28ab 100644
> --- a/drivers/regulator/twl-regulator.c
> +++ b/drivers/regulator/twl-regulator.c
> @@ -58,7 +58,7 @@ struct twlreg_info {
> struct regulator_desc desc;
>
> /* chip specific features */
> - unsigned long features;
> + unsigned long features;
>
> /*
> * optional override functions for voltage set/get
> @@ -1128,7 +1128,7 @@ static int twlreg_probe(struct platform_device *pdev)
> if (!initdata)
> return -EINVAL;
>
> - info = kmemdup(template, sizeof (*info), GFP_KERNEL);
> + info = kmemdup(template, sizeof(*info), GFP_KERNEL);
> if (!info)
> return -ENOMEM;
>
>
Acked-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2013-10-14 18:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 8:44 [PATCH 01/11] regulator: core: " Jingoo Han
2013-10-14 8:45 ` [PATCH 02/11] regulator: anatop: " Jingoo Han
2013-10-14 8:55 ` Shawn Guo
2013-10-15 12:21 ` Mark Brown
2013-10-14 8:46 ` [PATCH 03/11] regulator: fixed: " Jingoo Han
2013-10-15 12:22 ` Mark Brown
2013-10-14 8:47 ` [PATCH 04/11] regulator: lp3971: " Jingoo Han
2013-10-15 12:23 ` Mark Brown
2013-10-14 8:49 ` [PATCH 05/11] regulator: max8997: " Jingoo Han
2013-10-15 12:24 ` Mark Brown
2013-10-14 8:49 ` [PATCH 06/11] regulator: mc13783: " Jingoo Han
2013-10-15 12:25 ` Mark Brown
2013-10-14 8:51 ` [PATCH 07/11] regulator: mc13892: " Jingoo Han
2013-10-15 12:26 ` Mark Brown
2013-10-14 8:51 ` [PATCH 08/11] regulator: tps6105x: " Jingoo Han
2013-10-14 9:47 ` Linus Walleij
2013-10-14 8:52 ` [PATCH 09/11] regulator: tps65023: " Jingoo Han
2013-10-15 12:36 ` Mark Brown
2013-10-14 8:53 ` [PATCH 10/11] regulator: tps65910: " Jingoo Han
2013-10-15 12:38 ` Mark Brown
2013-10-14 8:55 ` [PATCH 11/11] regulator: twl: " Jingoo Han
2013-10-14 18:32 ` Nishanth Menon [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=525C38AB.3060002@ti.com \
--to=nm@ti.com \
--cc=balajitk@ti.com \
--cc=broonie@linaro.org \
--cc=jg1.han@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®