From: sre@kernel.org (Sebastian Reichel)
Subject: [Linux-kernel-mentees] [PATCH] Power: supply: abx500_chargalg.c: Fixed a code indentation error
Date: Sun, 20 Oct 2019 14:57:37 +0200 [thread overview]
Message-ID: <20191020125737.t4lx6nshoszojbtx@earth.universe> (raw)
Message-ID: <20191020125737.mwwtd0xELChP6WzNM0-S4E5QAV6WH7F_JOYC2T0g3H0@z> (raw)
In-Reply-To: <20191015161341.26868-1-madhuparnabhowmik04@gmail.com>
Hi,
On Tue, Oct 15, 2019 at 09:43:41PM +0530, madhuparnabhowmik04 at gmail.com wrote:
> From: Madhuparna Bhowmik <madhuparnabhowmik04 at gmail.com>
>
> Fixed Code indentation error caused due to using spaces
> instead of tabs.
> The error reported by checkpatch.pl is:
> ERROR: code indent should use tabs where possible
> The warning reported by checkpatch.pl is:
> WARNING: please, no spaces at the start of a line
>
> Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik04 at gmail.com>
> ---
Thanks, queued to power-supply's for-next branch.
-- Sebastian
> drivers/power/supply/abx500_chargalg.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/power/supply/abx500_chargalg.c b/drivers/power/supply/abx500_chargalg.c
> index 23757fb10479..e6e37d4f20e4 100644
> --- a/drivers/power/supply/abx500_chargalg.c
> +++ b/drivers/power/supply/abx500_chargalg.c
> @@ -354,13 +354,13 @@ static int abx500_chargalg_check_charger_enable(struct abx500_chargalg *di)
>
> if (di->chg_info.charger_type & USB_CHG) {
> return di->usb_chg->ops.check_enable(di->usb_chg,
> - di->bm->bat_type[di->bm->batt_id].normal_vol_lvl,
> - di->bm->bat_type[di->bm->batt_id].normal_cur_lvl);
> + di->bm->bat_type[di->bm->batt_id].normal_vol_lvl,
> + di->bm->bat_type[di->bm->batt_id].normal_cur_lvl);
> } else if ((di->chg_info.charger_type & AC_CHG) &&
> !(di->ac_chg->external)) {
> return di->ac_chg->ops.check_enable(di->ac_chg,
> - di->bm->bat_type[di->bm->batt_id].normal_vol_lvl,
> - di->bm->bat_type[di->bm->batt_id].normal_cur_lvl);
> + di->bm->bat_type[di->bm->batt_id].normal_vol_lvl,
> + di->bm->bat_type[di->bm->batt_id].normal_cur_lvl);
> }
> return 0;
> }
> --
> 2.17.1
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/linux-kernel-mentees/attachments/20191020/d7b42017/attachment.sig>
next prev parent reply other threads:[~2019-10-20 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 16:13 [Linux-kernel-mentees] [PATCH] Power: supply: abx500_chargalg.c: Fixed a code indentation error madhuparnabhowmik04
2019-10-15 16:13 ` madhuparnabhowmik04
2019-10-20 12:57 ` sre [this message]
2019-10-20 12:57 ` Sebastian Reichel
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=20191020125737.t4lx6nshoszojbtx@earth.universe \
--to=sre@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;
as well as URLs for NNTP newsgroup(s).