All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Saumya Ranjan Kuanr <saumyakuanr@gmail.com>, rjw@rjwysocki.net
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpu-idle: cpuidle-ux500: fixed a coding style issue
Date: Thu, 07 Nov 2013 10:25:34 +0100	[thread overview]
Message-ID: <527B5C8E.6030102@linaro.org> (raw)
In-Reply-To: <1382167729-21232-1-git-send-email-saumyakuanr@gmail.com>

On 10/19/2013 09:28 AM, Saumya Ranjan Kuanr wrote:
> Fixed a coding style issue
>
> Signed-off-by: Saumya Ranjan Kuanr<saumyakuanr@gmail.com>

Applied for 3.14.

Changed the subject to:

ux500: cpuidle: Fix indentation

Thanks
   -- Daniel

> ---
>   drivers/cpuidle/cpuidle-ux500.c |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpuidle/cpuidle-ux500.c b/drivers/cpuidle/cpuidle-ux500.c
> index e056465..746d716 100644
> --- a/drivers/cpuidle/cpuidle-ux500.c
> +++ b/drivers/cpuidle/cpuidle-ux500.c
> @@ -102,7 +102,7 @@ static struct cpuidle_driver ux500_idle_driver = {
>   			.exit_latency	  = 70,
>   			.target_residency = 260,
>   			.flags		  = CPUIDLE_FLAG_TIME_VALID |
> -			                    CPUIDLE_FLAG_TIMER_STOP,
> +						CPUIDLE_FLAG_TIMER_STOP,
>   			.name		  = "ApIdle",
>   			.desc		  = "ARM Retention",
>   		},
> --
> 1.7.9.5
>
>
>


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


      reply	other threads:[~2013-11-07  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19  7:28 [PATCH] cpu-idle: cpuidle-ux500: fixed a coding style issue Saumya Ranjan Kuanr
2013-11-07  9:25 ` Daniel Lezcano [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=527B5C8E.6030102@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=saumyakuanr@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 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.