Linux Power Management development
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: Munir Contractor <munircontractor@gmail.com>
Cc: linux-pm@vger.kernel.org
Subject: Re: [PATCH] power: Replaced spaces with tabs in indent
Date: Wed, 15 Mar 2017 22:21:51 +0100	[thread overview]
Message-ID: <20170315212151.y6uiiwcr62u5cd6g@earth> (raw)
In-Reply-To: <20170219231953.GA13155@munir-lfs>

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

Hi,

On Sun, Feb 19, 2017 at 06:19:53PM -0500, Munir Contractor wrote:
> This patch fixes 4 checkpatch.pl errors on lines 433 to 436:
> ERROR: code indent should use tabs where possible
> 
> Signed-off-by: Munir Contractor <munircontractor@gmail.com>
> ---
>  drivers/power/supply/ab8500_bmdata.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/power/supply/ab8500_bmdata.c b/drivers/power/supply/ab8500_bmdata.c
> index d298645..8c495860 100644
> --- a/drivers/power/supply/ab8500_bmdata.c
> +++ b/drivers/power/supply/ab8500_bmdata.c
> @@ -430,10 +430,10 @@ static const struct abx500_maxim_parameters ab8500_maxi_params = {
>  };
>  
>  static const struct abx500_maxim_parameters abx540_maxi_params = {
> -        .ena_maxi = true,
> -        .chg_curr = 3000,
> -        .wait_cycles = 10,
> -        .charger_curr_step = 200,
> +	.ena_maxi = true,
> +	.chg_curr = 3000,
> +	.wait_cycles = 10,
> +	.charger_curr_step = 200,
>  };
>  
>  static const struct abx500_bm_charger_parameters chg = {
> -- 
> 2.4.4
> 

Thanks, queued. I fixed up the subject while applying.
Also please always Cc mailinglists.

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

           reply	other threads:[~2017-03-15 21:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170219231953.GA13155@munir-lfs>]

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=20170315212151.y6uiiwcr62u5cd6g@earth \
    --to=sre@kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=munircontractor@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